github_enterprise_team_organizations_bulk_add

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

No annotations are available, so the description must convey behavioral traits. 'Add organization assignments' is too minimal to disclose side effects (e.g., whether it creates, updates, or overwrites assignments), required permissions, or idempotency. The tool is a mutation operation, but the description fails to provide critical behavioral context.

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 extremely short, but this is conciseness at the cost of clarity. It is a single phrase with no structure or prioritization of information. While not verbose, it lacks the substance expected for a tool with three parameters and no annotations.

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?

Given the tool complexity (three parameters, nested object, no output schema, no annotations), the description is insufficient. It does not explain what the body parameter expects, how results are returned, or the nature of 'organization assignments' in the enterprise context. The description leaves significant gaps for an AI agent to use the tool correctly.

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?

Schema coverage is 100%, but parameter descriptions are trivial ('enterprise', 'enterprise-team', 'Request body (JSON object)'). The description adds no additional meaning beyond the schema. Following the rule for high coverage, baseline is 3, though the schema descriptions themselves are minimally informative.

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 organization assignments' identifies a verb and resource, but is vague. It does not clarify what 'organization assignments' means (e.g., assigning organizations to an enterprise team or vice versa) and fails to distinguish from the sibling tool 'github_enterprise_team_organizations_add' which likely performs a singular add. The bulk nature implied by the name is not articulated.

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 guidance is provided on when to use this tool versus alternatives like singular 'add' or 'bulk remove'. There is no mention of context, prerequisites, or scenarios where this tool is appropriate. The description is entirely silent on usage direction.

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