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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so safety is covered. The description adds content-level context (sourced basis, as-of dates implying data freshness), but says nothing about behavior such as unknown-name handling or rate limits, and much of it restates return payload that the output schema already defines.

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?

A single front-loaded sentence that leads with the resource and scope, then enumerates payload contents. Slightly list-heavy, but every element is a distinct, useful field category rather than filler.

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 one-parameter read tool with full annotation coverage and an output schema, the description covers what the record contains and that it is sourced, so an agent has enough to invoke it correctly. The remaining gap is routing guidance against sibling tools, which is not strictly required here.

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?

Only one parameter and schema description coverage is 100%, so the schema fully documents 'name' including its naming convention. The description adds no syntax or format detail beyond that, so the baseline of 3 applies.

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+resource ('Full sourced record for one platform') and enumerates the payload: per-criterion scores, incidents, regulatory actions, as-of dates, page URLs. An agent can tell this is the detail-fetch counterpart to a list/search, though no sibling is named explicitly.

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?

Usage is only implied: 'for one platform' suggests a single-record lookup following a listing, and the sibling search_platforms is referenced only inside the parameter schema, not the description. No when-not or explicit alternative (search_platforms, check_platform_safety, compare_platforms) is stated.

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