create_project_collaborator

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

Annotations already indicate destructiveHint=false and idempotentHint=true, which describe core behavioral traits. The description adds nothing beyond that, but does not contradict annotations. It does not disclose edge cases like duplicate collaborator handling, but the annotations carry the burden here.

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, focused sentence with no wasted words. It is front-loaded and easy to parse, effectively conveying the core action.

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 complexity (one parameter but a nested object with four required fields) and the presence of an output schema, the description is minimally adequate. However, it lacks information on error cases, permissions, and behavior when adding an existing collaborator. For a CRUD tool with many siblings, more context would be beneficial.

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 description coverage is 0% because the tool description does not mention any parameters. The input schema includes a nested object with four required fields, each with its own description. However, the tool description fails to explain the structure or required fields, leaving the agent to rely entirely on the schema.

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 a collaborator to a project' clearly states the verb (add), the resource (collaborator), and the scope (to a project). It distinguishes from sibling tools like delete_project_collaborator, update_project_collaborator, and read_project_collaborators, which handle other CRUD operations.

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?

The description provides no guidance on when to use this tool versus alternatives like update_project_collaborator for modifying permissions or delete_project_collaborator for removal. It also lacks prerequisites, such as whether the caller needs specific permissions or if the project must exist.

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