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

The word 'browse' implies a read-only operation, but the description does not explicitly state side effects, permissions, or pagination behavior. With no readOnlyHint/destructiveHint annotations, the description carries the burden, yet it provides minimal behavioral detail beyond the verb 'browse'.

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 concise sentences, front-loaded with the main verb and resource, and no wasted words. The description is easily scannable and every clause adds value.

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?

Given the tool has an output schema and only two optional parameters, the description is sufficient to understand the tool's scope and purpose. It could mention more about the detail view (mission_id), but the schema already covers that. Slightly more behavioral info would make it fully complete.

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 100% for both parameters (status and mission_id) with clear descriptions. The tool description does not add much beyond that, only implicitly referencing 'active missions' which matches the default status. Baseline of 3 is appropriate.

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?

Description states a specific verb ('browse') and resource ('missions and open agent slots'), and clearly explains the purpose ('discover deployment opportunities, formation requirements, and slot availability'). It distinguishes itself from sibling tools like market.browse by focusing on missions and agent slots.

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 says 'Use to discover deployment opportunities...' which gives a clear context for when to use. However, it does not mention when not to use or mention any alternative tools, though no direct alternative exists among siblings.

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