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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safe read profile is covered. The description adds the field list and batch behavior, but does not disclose additional behavioral details such as output shape, pagination, or rate limits. This is acceptable given annotation coverage, but not exceptional.

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 with no filler: the first states the purpose and enumerates returned fields, the second covers the batch format. Both sentences earn their place and the most important action is front-loaded.

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?

For a single-parameter, read-only tool, the description covers what resource is fetched, what fields are included, and how to batch requests. The absence of an output schema is partially mitigated by the field list. It does not state the exact response container for batch requests, but this is minor.

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?

The input schema already provides 100% parameter documentation, explaining IDs, slugs, comma-separated batch format, and the ALWAYS-use-batch rule. The description's batch mention adds no new semantic value beyond what the schema already covers, so the baseline of 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?

Uses a specific verb-resource pair ('Get complete details for businesses') and enumerates the exact fields returned (address, phone, website, hours, services, etc.). This makes the tool's scope clear and distinguishes it from search-oriented siblings like search_businesses.

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 explicit guidance on when to use this tool versus alternatives. The description and schema mention batching, but do not state when to choose get_business over search_businesses, list_categories, or get_rankings, nor provide prerequisites like needing known IDs or slugs.

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