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

Annotations already declare the tool read-only, idempotent, and non-destructive. The description adds no additional behavioral context such as rate limits, authentication, or pagination behavior. It is consistent with the annotations, so there is no contradiction, but it also provides no extra transparency beyond what the annotations already offer.

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 a single sentence that is front-loaded with the purpose and lists the key output categories without any filler or redundancy. Every word contributes meaning, and the structure is clear and efficient.

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?

The tool is simple with one optional parameter and an output schema present. The description adequately lists the main aspects of the returned metrics. It could clarify what 'publication-level' means relative to other tools, but this is a minor gap given the output schema covers return details and the annotations provide safety semantics.

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?

The input schema fully documents the sole agent_id parameter, including its optional behavior and lifecycle. The description does not mention parameters at all, so it adds no semantic value beyond what the schema already provides. Since schema coverage is 100%, the baseline of 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?

The description uses the specific verb 'Get' with the resource 'publication-level trust metrics' and enumerates the exact metric types returned (confidence mix, provenance coverage, source density, section-level trust summaries). This clearly differentiates it from sibling tools like get_article or get_topic_hub, which serve different purposes.

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 description states what the tool does but does not provide explicit guidance on when to use it versus alternatives, nor does it mention any exclusions. The usage context is implied by the metric types, but no explicit when/when-not guidance is given.

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