github_enterprise_team_organizations_add

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, and the description gives no behavioral details such as permissions required, side effects, or idempotency. The description simply states 'Add', which implies mutation but offers no further transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, making it concise. However, it is under-informative; brevity comes at the expense of clarity. A slightly longer description could provide needed context without being verbose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is a mutation with three required parameters and no output schema. The description fails to explain what happens after adding (e.g., success response, errors, or effects on existing assignments). This leaves the agent without crucial context for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% coverage but parameter descriptions are tautological (e.g., 'enterprise' described as 'enterprise'). The main description does not add any meaning beyond the parameter names. With no additional context, an agent cannot infer the correct values or constraints.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Add an organization assignment' provides a verb and resource, indicating the action is adding. However, it doesn't clarify what 'organization assignment' entails or differentiate from sibling tools like 'bulk_add' or 'get_assignment'. The purpose is clear at a basic level but lacks specificity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

No usage guidance is provided. The description does not specify when to use this tool versus alternatives like bulk_add or delete. Sibling tools exist but no context is given, making it difficult for an agent to decide when to invoke this tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.