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

With no annotations, the description carries full behavioral burden. It discloses that the manageKey is shown exactly once, losing it is irreversible because rotate_key needs the current key, the result includes a manageKeyNotice, and settlement is manual during alpha. This is rich, safety-critical context beyond a simple 'post' action.

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 compact—four short sentences—and front-loaded with the primary purpose. It then delivers a critical warning, result notice, and settlement caveat in a logical order with no redundancy, earning a top score.

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?

The description covers the most contextually unique aspects—the manage key lifecycle and manual settlement—but for a complex tool with 14 parameters, no output schema, and no annotations, it leaves gaps. It does not mention the response structure beyond the notice or clarify parameter semantics, making it only minimally 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?

The schema has 0% property descriptions, and the description does not compensate by explaining the meanings or relationships of the 14 parameters. It only implies mission details but leaves fields like fundingUrl, submissionCap, and routingDecisionId undefined, forcing the agent to guess from names.

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 states the tool posts a public Birdfury mission and mints a one-time bf_post_ manage key, which is a specific verb+resource combination. This distinguishes it from siblings like claim_mission or list_missions, leaving no ambiguity about what the tool does.

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 provides clear context for when to use the tool—posting a public mission and handling the manage key—but it does not explicitly name alternatives or exclusions. Since the primary action is explicit, it earns a 4 rather than a 5, which would require explicit when-not-to-use guidance.

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