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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safe-read profile is covered. The description adds no further behavioral context such as id format requirements, error behavior on unknown ids, or data freshness, so with the annotations carrying the burden this lands at a baseline 3.

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?

A single short sentence with no filler, and the resource is front-loaded. It is efficient, though so terse that it conveys almost nothing an agent could not derive from the name alone.

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 one-parameter read tool with an output schema present, return values need no explanation and the sole parameter is fully documented in the schema. The description is complete enough to invoke correctly, missing only usage routing to sibling search/facets tools.

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 description coverage is 100% and the schema itself explains the '<bbbLocalId>-<businessId>' slug format from the profile URL. The description contributes nothing beyond restating 'business id', so baseline 3 is correct.

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 and retrieval action ('BBB businesses dataset record by business id'), which clearly distinguishes a single-record lookup from the sibling datasets_bbb_businesses_search and _facets tools. It stops short of explicitly naming those siblings, so an agent must infer the split from the tool name.

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 statement of when to use this tool versus datasets_bbb_businesses_search or datasets_bbb_businesses_facets, and no prerequisite such as 'call search first to obtain an id'. Usage is only implied by 'record by business id' and the _item suffix.

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