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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered and the bar here is lower. The description adds real value by enumerating exactly what evidence is returned (score arithmetic, gates, carriers, neighbors, exclusions), which matters because there is no output schema. It says nothing, however, about failure modes — e.g. what happens if item_id is unranked or the date/edition yields no story.

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 whole definition is a single ~70-word run-on sentence with a nested parenthetical, no front-loaded summary, and no separation of purpose from return contents. Every clause carries information, so there is little pure filler, but the lack of structure makes it hard to parse quickly.

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?

With no output schema, the description correctly spends its budget describing the return payload, which is the right call for a diagnostic explainer. Against that, a 3-parameter tool at 0% schema coverage gets no parameter documentation and no usage context, so an agent can know what comes back but not confidently how to call it.

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 0%, so the description carries the full burden for item_id, date and edition, and it largely fails: 'a piece' only obliquely implies item_id, and 'at the edition's home and at the world' hints at the edition parameter/default without stating allowed values, while date is never addressed at all. The heavy return-value detail does not compensate for undocumented inputs.

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 conveys that this explains why a piece sits where it does on the list — its rank, score and the factors behind them — so the general intent is inferable. But the purpose is delivered as an unlabeled inventory of return contents ('mains', 'pulls', 'stakes', 'gates') rather than a stated verb+resource, and several terms are undefined domain jargon. It also makes no attempt to distinguish itself from siblings like top or search, which an agent would plausibly confuse it with.

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 when-to-use guidance, no prerequisites, and no naming of alternatives. An agent gets no signal about whether to call this after search/top, or what makes a piece eligible to be explained. Usage must be entirely inferred from the sibling list.

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