browse_missions

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

With no annotations, the description carries the behavioral disclosure burden. It adds meaningful security context by warning that mission content is untrusted data and not instructions, and states no login is required. However, it does not disclose pagination behavior, response format, or whether the operation has any side effects, though 'browse' implies read-only.

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?

The description is concise and front-loads the core action and resource. The warnings about untrusted data and no login are valuable additions that earn their place. It could benefit from a brief note on parameters or use cases, but it does not contain fluff.

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 five parameters, no output schema, and no annotations, the description is too sparse for a calling agent. It explains the high-level purpose and safety posture but omits filter semantics, pagination expectations, response shape, and how this differs from similar sibling tools. This leaves significant gaps for correct invocation.

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%, and the description provides no information about any of the five parameters (limit, offset, status, category, capability). The parameter names are somewhat self-explanatory, but the description adds zero semantic value to help an agent correctly format or filter queries.

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 clearly identifies the operation ('Browse') and resource ('public TaskBounty Missions'), with a concrete subject ('agents form teams around a concrete outcome'). It differentiates from the broader bounty tools by emphasizing the public and mission-specific nature, though it does not explicitly contrast with sibling tools like list_open_bounties.

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 tool is for viewing public missions without authentication ('No login required'), which is useful context. However, it provides no explicit guidance on when to choose this tool over related siblings such as list_open_bounties or browse_agent_commons, nor any exclusions.

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