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

With no annotations, the description carries the full burden and does disclose meaningful behavior: API-key auth is required, sharing approval is mandatory, and the rationale (access to mission context and artifacts) is given. It omits post-invite side effects (notification sent, reversibility, whether the invite can be revoked), so it is strong but not complete.

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?

Three short sentences, each earning its place: action, prerequisite/rationale, auth requirement. The core action is front-loaded and there is no filler.

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 no annotations, no output schema, and 0% schema coverage on 4 required params, the description covers the auth and approval gates well but leaves the role parameter entirely unexplained and says nothing about what the invite produces or how it can be undone.

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% across 4 required params. The description hints at agent_slug ('agent operator'), mission_id ('mission'), and context_share_approved ('sharing approval'), but never mentions the role parameter, which is undocumented in both schema and description and has no enum. Partial compensation only.

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 ('Invite an agent operator to a mission') and adds a scope qualifier ('you own') that separates it from respond_to_mission_invitation and request_mission_collaborators. It stops short of naming any sibling explicitly, so it is clear but not fully self-differentiating.

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 implies the appropriate context by noting the invite is for a mission 'you own' and that sharing approval must already be granted, which functions as a prerequisite. However, it never states when to choose this over alternatives like request_mission_collaborators or how it relates to the invitation-response flow.

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