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

With no annotations provided, the description fully accounts for behavioral transparency. It discloses that absent information is named in a 'missing' field (not dropped silently), unknown slugs return candidate slugs, and no authentication is needed. This covers important edge cases and safety considerations.

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 concise and well-structured, front-loading the core purpose and then adding relevant details about missing fields, error handling, and authentication. Every sentence serves a purpose without redundancy.

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 no output schema, the description is highly complete: it lists the categories of returned data, explains the 'missing' field convention, describes behavior for invalid slugs, and confirms no credentials are needed. This enables an agent to confidently invoke the tool.

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%, but the description adds value beyond the schema by explaining the default fallback logic for the 'kind' parameter (entity then website) and specifying that 'slug' comes from a search_businesses result. This provides essential context beyond parameter names and enum values.

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 reads the full business profile, listing specific fields like identity, contact, address, social profiles, offerings, FAQ, and verification. It distinguishes from siblings like search_businesses (searching) and contact_business (contacting) by focusing on reading a complete record.

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?

The description notes the tool requires no credentials and explains behavior for unknown slugs, but does not explicitly state when to use this tool over alternatives like search_businesses or contact_business. However, the context is clear enough for an agent to infer appropriate use.

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