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

Beyond the readOnlyHint annotation, the description adds substantial behavioral context: exactly what the response contains (hints.similar, per-trader realized profit, close/expiration times), the 404 trigger condition, and the fact that the 404 payload carries a fallback search hint. It also states no API key is needed — a non-obvious operational fact.

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 front-loaded with the returned record and capped by the 404 behavior, with no redundant sentences. The one long enumeration of fields is dense but earns its place for an open-world record tool.

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 single-resource read with no output schema, the description fully covers what is returned, the failure mode, and the fallback path, leaving no meaningful gap 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 100% (the ticker param already documents 'Kalshi market ticker'), so the baseline is 3. The description does not add syntax or format constraints beyond what the schema pattern provides.

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 precise verb and resource ('Full record of one settled Kalshi market this roster won') and enumerates the returned fields. It is clearly distinguishable from the sibling search_settled_wins, which searches rather than returns a single record.

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 404 semantics act as implicit usage guidance: if the ticker is not an archived win, the agent is told to fall back to searching the series. However, it does not explicitly contrast this tool with search_settled_wins for the case when the agent only has a series-level question.

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