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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds some value by stating the read is 'private' and scoped to 'your own' data, which the annotations do not convey. It does not describe auth requirements or the contents/format of the returned report.

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?

A single well-formed sentence that front-loads the ownership/privacy constraint and the operation. No filler or redundancy, though it is arguably too sparse given the missing usage and return detail.

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 read-only tool with no output schema, the description should carry more weight about what comes back. It names the returned content at a high level ('claim, eligibility state and structured report') but leaves the report's structure and the conditions under which eligibility state varies unexplained.

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 50%: agent_key is fully documented in the schema, and claim_id is constrained by a regex pattern, so the schema carries most parameter meaning. The description only loosely implies that claim_id identifies 'your own market decision claim' and adds no format or sourcing detail beyond the schema.

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') and resource ('your own market decision claim, eligibility state and structured report'), making the operation identifiable. However, it does not differentiate itself from the close sibling speedbot_claim_market_decision, leaving the agent to infer whether this reads a claim or creates one.

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?

There is no statement of when to use this tool versus alternatives such as speedbot_claim_market_decision, speedbot_decide, or speedbot_directed_test_report. Usage is only weakly implied by the word 'your own' and the resource it names.

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