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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description goes beyond that by disclosing the response structure, the ordering of evidence_strength_reasons ('each rule that set the level, in order'), and what the assessment does not weigh.

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?

Front-loaded with the resource and then the payload, followed by one usage sentence. The long enumerated clause is dense but every element earns its place; minor compression is possible.

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?

No output schema exists, so the description carries the return-value burden and does so thoroughly, listing every field and the semantics of evidence_strength_reasons. Nothing needed to call it correctly is missing.

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 coverage is 100% and the single parameter is already documented with its pattern and source. The description adds the concrete permalink shape ('the last part of a permalink, /e/{id}'), which meaningfully supplements the schema's generic 'from a permalink or get_findings'.

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?

States a specific verb (get) and resource (one finding by id) and enumerates exactly what comes back: claim, evidence strength and its meaning, verbatim quote, study design, paper, and evidence_strength_reasons. The singular 'One finding' cleanly separates it from the sibling get_findings.

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?

Gives an explicit use case: 'Use it to explain why the evidence behind a finding is as strong as it is, from evidence_strength_reasons rather than by guessing.' It also tells the agent where the id comes from (permalink or get_findings), but it does not explicitly name alternatives or exclusions.

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