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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds useful context about what data is returned and that ranking is included by default, but says nothing about rate limits, auth, or pagination.

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 payload description before the endpoint path. The GET path is somewhat redundant for an agent but is compact and does no harm.

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?

With no output schema, the description carries the burden of describing the return, and it does so by enumerating the fields. It's largely sufficient for a read-only lookup; only edge details like pagination or empty-result behavior are missing.

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%, so all five parameters are documented in the schema, including the 'false is faster' hint on include_ranking and the period semantics of start/end. The description reinforces the default-ranking behavior for the period but adds no syntax or format detail beyond the schema, so 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 names a specific resource (one tracked keyword) and enumerates what comes back — groups, volume, CPC, difficulty, ranking — which differentiates it from siblings like wincher_list_keywords and wincher_get_keyword_ranking_history. It stops short of explicitly naming those alternatives, but the single-keyword scope is unmistakable.

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: 'One tracked keyword' suggests this is the single-item lookup versus wincher_list_keywords for many, but no when-to-use, prerequisites, or alternative routing is stated. It also doesn't note the parent id dependencies (website_id from wincher_list_websites) that live only in the schema.

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