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

With no annotations, the description carries the behavioral burden and does add useful return-content detail (services, hours, contacts, photos, FAQs, products, freshness). However, it does not explicitly state that this is a read-only operation, nor does it mention auth, failure behavior, or rate limits.

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?

It is a single front-loaded sentence with a dense, well-organized list of returned fields and no filler. Every phrase adds information about what the tool returns.

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 simple one-parameter read tool with no output schema, the description does the important work of enumerating the profile contents. Its main gap is the absence of any behavioral or error-handling context, but the core retrieval scope is well covered.

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 schema has 100% description coverage for the single id parameter, so the baseline is 3. The description does not add further meaning beyond what the schema already provides for that parameter.

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 business') and clearly states it returns a full profile, unlike the broader search_businesses tool. It does not explicitly contrast itself with get_changes, but the purpose is still easy to distinguish from both siblings.

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 does not say when to use this tool versus search_businesses or get_changes, nor does it describe prerequisites such as obtaining an id first. The intended use as a detail-fetching follow-up to search is only implied by the schema parameter description.

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