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

Annotations already state readOnlyHint=true, idempotentHint=true, closed-world, and non-destructive, so safety is covered. The description adds only the scoping detail 'across all its keywords over a window'; it says nothing about ordering, aggregation, or how the history is presented.

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 sentence with no filler, and the application-wide scope is stated early. The terseness contributes to ambiguity, but structurally it is 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 operation is low-complexity and the schema is fully documented, so the essentials are present. However, for a 'history' tool with no output schema, the description should better explain what is returned or how observations are ranked over the window.

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%, with both application_id and days fully documented including the default and max. The description adds little beyond 'over a window' and does not clarify whether days affects ranking scope or history depth.

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 names a verb ('Rank') and resource ('observations for an application across all its keywords over a window'), but 'Rank observations' is vague and does not clearly convey that this retrieves score history over time. It also fails to distinguish itself from the sibling get_keyword_rank_history, which sounds closely related.

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 guidance on when to use this tool versus alternatives such as get_keyword_rank_history, get_dashboard, or get_application. The window parameter is mentioned only indirectly through 'over a window,' with no conditions or exclusions.

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