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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds real value beyond that: it discloses the sort order ('newest first') and a substantive caveat that 'Verdicts are the edition's assessment as of its date', warning the agent that verdicts are point-in-time snapshots rather than current judgments.

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?

Two sentences, front-loaded with the resource and then the payload contents, ending with the usage cue. The enumeration of returned fields is dense but each item is informative; the only mild redundancy is restating the resource name in the second sentence.

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?

There is no output schema, so the description correctly compensates by listing the returned fields (claim text, speaker, date, verdict, analysis, edition date, URL, citeAs). Combined with annotations covering the safety profile, an agent has what it needs to call this correctly; only pagination behavior for the limit is left implicit.

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 a single parameter at 100% schema description coverage, the schema already documents limit ('How many, 1 to 50. Default 10.'). The description contributes only indirectly via the 'newest first' ordering, which implies the limit truncates the most recent entries; it never mentions the parameter, its range, or the default. Baseline 3 is appropriate.

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?

Names a specific resource (the Claim of the Week fact check from Straight Record Sunday editions) with a verb-like scope and an ordering guarantee ('newest first'). It enumerates what each record contains, so an agent knows exactly what it is retrieving. It stops short of explicitly contrasting itself with the sibling get_straight_record_edition, which is the closest potential confusion.

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?

'Use for what The Straight Record has fact-checked' gives a positive usage context, which is more than nothing. However, there is no exclusion guidance and no pointer to alternatives such as get_straight_record_edition for full editions or search for targeted lookups, so an agent must infer the boundary itself.

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