add_template_collaborator

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

With no annotations, the description carries the full burden of disclosing side effects. It does mention the invitation email, which is useful behavioral information. However, it omits that this is a mutating operation on the template's collaborator list, whether the access persists, what permissions are needed, or how the action can be reversed.

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 short and front-loaded with the primary action, followed by the conditional email behavior. It is efficient with no fluff, though the double period and 'a HTTPS' grammar issue make the text feel slightly unpolished.

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?

There is no output schema and no annotation coverage, so the description should explain what the tool returns, but it never states whether the generated HTTPS link is the return value. It also does not cover permission requirements, reversibility, or how this affects existing collaborators. For a mutation tool with optional email side effects, this is a significant completeness gap.

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 schema already describes name and email, and the description mostly restates the email-to-invitation behavior. It adds some context by clarifying that the tool creates an editing link for the template, which helps explain the purpose of template_id. It does not add meaningful detail about name or any parameter 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 gives a specific outcome: creating an HTTPS link for editing a contract template and conditionally sending an invitation email. The action is concrete enough for an agent to understand the tool's basic function. However, it never explicitly says it 'adds a collaborator' to a template, so part of the core meaning relies on the tool name rather than the description.

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?

There is no guidance on when to choose this tool over alternatives such as remove_template_collaborator or list_template_collaborators. The description only explains what the tool does, leaving the agent to infer usage context from the tool name and sibling list. No exclusions or alternative routing are provided.

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