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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds the multi-location URL handling nuance, but says nothing about rate limits, error behavior, or auth beyond what annotations provide, so a baseline-plus score is appropriate.

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 tightly written sentences with the action front-loaded, followed by the source/location nuance and the return summary. No filler and no repetition.

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 read-only single-fetch tool with annotations covering safety and an output schema covering return shape, the description is nearly complete; the only minor redundancy is listing return fields that the output schema already documents.

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 single parameter has 100% schema coverage, giving a baseline of 3, but the description adds genuine semantic value by explaining when to pass hq_profile_url versus url (multi-location businesses), which the schema only lists without distinguishing.

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 uses a specific verb ("Fetch") on a specific resource ("one Better Business Bureau profile") and scopes it to a single record, which cleanly separates it from the sibling search tool bbb_search. An agent can immediately tell this is the profile-detail endpoint.

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 explicitly states where the input comes from ("using its required profile URL from bbb_search") and names the multi-location variant condition ("use hq_profile_url for a multi-location business"). This is clear context, though it does not explicitly exclude sibling detail tools like bbb_business_complaints or bbb_business_more_info.

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