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

Annotations cover mutation/idempotency but the description adds substantial context beyond them: it does not send email on its own, requires owner/admin privileges, returns email/role/workspace/revision to surface to the user, and clarifies that membership grants no dossier access or business approval. This is rich behavioral disclosure.

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?

Front-loaded with purpose and scope, then authorization and workflow guidance. Every clause earns its place, though the sentence is dense with several distinct obligations packed together rather than cleanly separated.

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?

For a mutation tool with annotations and no output schema, the description covers the essential concerns: auth requirements, the non-mutating-until-confirmed workflow, what to surface to the user, and the limited scope of membership. Nothing critical is missing.

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 only 25%, so the description must help. It explains 'exact email' and enumerates the viewer/contributor/reviewer role values, matching the enum. However, it adds nothing about the locale parameter, and idempotencyKey meaning comes only from the schema, not the description. Adequate but leaves a gap.

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?

States a specific verb and resource ('Prepare a workspace invitation'), enumerates the exact role values, and clearly delineates the scope from its sibling send_workspace_invitation by noting it 'Does not send email'. An agent can distinguish it from the send sibling without opening either schema.

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?

Explicitly restricts the caller ('Owner/admin only'), explains the non-send behavior, and prescribes the workflow: show the returned values and 'only call send after the user explicitly authorizes that exact invitation'. This names both the condition and the alternative tool.

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