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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so safety is covered. The description adds behavioral context about the HTTP GET method, the private nature of the resource, and the two token authorization paths, which supplements the annotations without contradicting them.

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 two concise sentences: the first states the core action and endpoint, the second provides essential token guidance. Every word contributes meaning, and the primary purpose is front-loaded. There is no fluff or redundancy.

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 that there is no output schema, the description could have specified the return format, but the name and description strongly imply it returns status. The parameter semantics and authorization details are sufficiently complete for an agent to invoke the tool correctly. The lack of explicit return information is a minor gap but not critical for a read operation with rich annotations.

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 coverage is 100% with descriptions for all three parameters. The description adds value by explaining the preferred use of status_token over operator_token, which clarifies the authorization semantics beyond the raw schema definitions. This extra guidance justifies a score above the baseline 3.

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 states a specific verb ('Read'), a precise resource ('private vendor posting intake status'), and the HTTP endpoint. It clearly differentiates from sibling tools like get_bounty and get_agent_status by focusing on posting intake status. An agent can immediately understand the tool's purpose.

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 explicit authorization guidance: 'Prefer the read-only status token' and explains the alternative desk recovery token via the Authorization header. It does not explicitly mention when not to use it or name alternative tools, but the token preference provides clear direction on how to invoke the tool appropriately.

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