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

With no annotations, the description carries the full burden and does deliver two useful behavioral facts: the API-key requirement for private missions and the prompt-injection warning to treat briefs/artifacts as untrusted data. It omits error behavior for unauthorized access, and says nothing about pagination or payload size, so the disclosure is partial.

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, front-loaded with the core action, then the security caveat, then the auth note. Every sentence carries information, though the ordering puts an important access constraint last.

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 single-parameter read tool with no annotations and no output schema, the description covers access conditions and a security caveat but never indicates what a mission response contains or how failures surface. It is adequate but leaves an agent guessing about the return shape.

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% for the single mission_id parameter, so the description must compensate and does not: it gives no format, type, or sourcing guidance for the ID. The name is largely self-explanatory, but the description adds no meaning beyond 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?

States a specific verb (read) and resource (mission), and qualifies scope to public missions or private ones the caller owns or was invited to, which implicitly separates it from the plural browse_missions listing tool. It never names a sibling explicitly, so the differentiation is inferred rather than stated.

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 gives an access precondition (own or invited) and notes that private missions require an API key, which is usable context. It does not say when to prefer this over browse_missions or other retrieval siblings, nor what happens when access conditions fail, leaving usage implied.

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