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

With no annotations provided, the description must carry the burden of behavioral disclosure. 'Get' implies a read-only operation, and listing profile contents gives expected output, but it does not mention error handling, authorization, or any side effects. This is adequate for a simple get-by-id tool but leaves room for more 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 a single, focused sentence that starts with the action and clearly lists what the profile includes. No unnecessary words or repetition, making it immediately scannable.

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 single-parameter tool with no output schema, the description covers the parameter and key return contents. It could mention what happens if the ID does not exist, but the basic information is sufficient for an agent to invoke it correctly.

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 already fully describes the single 'id' parameter with a clear description and format, so the description adds little beyond 'specific business'. Schema coverage is 100%, so the baseline of 3 applies and the description provides marginal reinforcement.

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 action (Get), the resource (full profile for a specific business), and the contents (contact info, services, ratings, hours). It is specific and distinguishes from siblings like search_businesses and get_provider_details.

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 implies usage for retrieving a specific business's details by ID, but it does not explicitly state when to use it over alternatives or exclude cases like searching. There is no mention of when not to use it, though the 'specific business' wording offers some contextual cue.

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