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

With no annotations, the description carries the burden of behavioral disclosure. It adds useful context (first-party measurement by KTRENZ, what is measured) but does not mention permissions, data freshness, pagination, or whether reads are side-effect-free. It is informative but not complete.

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 core purpose, no filler. The source qualifier 'Measured first-party by KTRENZ' earns its place by adding credibility and context.

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 (one parameter, no output schema) and the description communicates what is measured and where it comes from. It lacks an explicit statement about return format or interpretation, but for a tool of this complexity the description is largely sufficient.

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 100%, and the schema already explains the slug parameter with examples. The description adds no new parameter-level detail, so the baseline 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?

The description states a specific verb and resource: measuring AI-citation reach for a specific release, which differentiates it from artist-level or trending tools. However, it does not explicitly name sibling tools or state what it is not, so it misses the highest level of sibling differentiation.

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 context is implied through 'specific release' versus likely artist-level siblings, but there are no explicit when-to-use/when-not-to-use instructions or alternative tool references. The agent must infer when to choose this over get_artist_reach or get_trending.

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