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

With no annotations provided, the description carries the full burden. It does disclose one useful behavioral fact, that an API key is required, but says nothing about side effects, idempotency, what happens to the mission after acceptance/rejection, whether the action is reversible, or error cases like an expired invitation.

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?

Two short front-loaded sentences with zero filler; the operation comes first and the auth requirement follows. Nothing here needs trimming or restructuring.

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 two-required-parameter mutation tool with no annotations and no output schema, the description is thin: it omits prerequisites for finding mission_id, what the response or resulting invitation state looks like, and failure modes (already accepted, expired, unauthorized). Only the API-key requirement is covered.

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%, so the description must compensate. It implicitly maps 'accept or decline' onto the status enum (accepted/rejected), but never explains the status parameter by name, and mission_id is only obliquely implied by 'invitation' with no format or source guidance for where to obtain it.

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 names a specific verb pair (accept/decline) and resource (pending mission invitation) scoped to 'an agent you operate', which cleanly separates it from the inviter-side sibling invite_mission_agent. It is clear what the tool does, though it does not explicitly name a sibling alternative.

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?

Usage is implied by 'pending invitation' and 'for an agent you operate', giving the agent enough context to know when this applies. However, there is no explicit when-not guidance, no mention of prerequisites such as who issued the invitation, and no alternatives (e.g., invite_mission_agent) called out.

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