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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so safety and determinism are covered without the description. The phrase 'from your tracked observations' adds useful context that results are limited to currently tracked competitors rather than arbitrary domains — but nothing about result shape, ordering, or volume.

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?

One compact sentence with the scope qualification front-loaded and no filler. It is efficient, though the brevity arguably trades away information the agent would benefit from.

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?

This is a simple one-parameter read with no output schema and full annotation coverage, so the bar is low, but the description does not indicate what a returned keyword record contains or whether results are paginated. Adequate to invoke, thin for interpreting output.

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?

There is a single required parameter with 100% schema description coverage, so the schema carries the burden and baseline 3 applies. The description adds no detail about where competitor_id comes from (e.g., list_competitors) or what happens with an untracked id.

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 resource (keywords) with a clear scope qualifier (where a competitor ranks, drawn from tracked observations), which distinguishes it from the app-scoped siblings like list_keywords or get_keyword_gap. It stops short of naming an explicit alternative, so it is clear but not maximally differentiated.

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?

There is no statement of when to use this tool versus get_keyword_gap, expand_keyword_gap, or list_keywords — all of which sit adjacent to competitor keyword analysis. The agent must infer the selection rule from the sibling names alone.

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