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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds unique behavioral context: rankings are based on 'real user click-through data,' which is not inferable from annotations or schema. It also mentions the area/category scope, enhancing transparency.

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?

The description is two sentences, front-loaded with the primary action and resource. The second sentence clarifies intended usage. No filler or redundant information.

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?

Given the tool's moderate complexity (5 params, no output schema), the description is sufficient for an agent to select and invoke it. It explains the tool's purpose, data source, and usage context. It does not describe return format, but that is not required for a simple read-only rankings tool with clear annotations.

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%, so parameters are fully documented. The description adds a slight hint by referencing 'area' and 'category', which map to the country/city and category parameters, but it does not add syntax or format details beyond what the schema already provides. 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 clearly states the tool's function: 'Get the most popular businesses in an area, ranked by real user click-through data.' This specific verb+resource+scope distinguishes it from siblings like get_business (single business) and search_businesses (likely search-based). The additional phrase 'Use to find top-rated businesses by category' adds further specificity.

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?

It provides clear usage context: 'Use to find top-rated businesses by category.' This implies when you need rankings based on popularity. It does not explicitly mention alternatives or exclusions, but the sibling set and description give enough context for an agent to choose this tool over a generic search.

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