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

Annotations already establish read-only, idempotent, non-destructive behavior. The description adds valuable context beyond those annotations by prescribing the initial guide step, the ordered inspection sequence, and the critical domain rule that only CompetitionSettledV2 counts as payment evidence. No contradiction with annotations.

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, each carrying essential information: the starting operation, the ordered list of what to inspect, and the payment-evidence caveat. There is no filler, repetition, or unnecessary restatement of the tool name.

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 schema with multiple oneOf branches and an output schema, the description provides the necessary workflow guidance and a domain-critical caveat. It is enough for an agent to start with guide and follow the operation-specific fields, though it relies on the schema for detailed parameter constraints and does not explicitly address sibling tool selection.

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?

With 0% schema description coverage, the description must compensate for missing parameter explanations. It does map operation values to their meanings and instructs the agent to use only fields accepted by the selected operation. However, network defaults, state filtering, bounty_id format, and job_id semantics are left to the schema's enums and patterns, so the compensation is partial.

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 identifies the tool as an inspection/read tool for the V2 competition and enumerates the specific read surfaces: release, profiles, inventory, events, and proof-job state. It is clearly distinct from sibling preparation tools like prepare_open_competition_v2, though the distinction is implied rather than explicit.

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?

It gives an explicit workflow: new users should start with operation=guide, then follow the returned order for inspecting other data, and treat only CompetitionSettledV2 as payment evidence. This is clear usage context, but it does not explicitly discuss when to prefer this tool over its siblings.

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