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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=false, so the write/safety profile is covered structurally. The description adds useful scope context about what is not created, but says nothing about permissions, duplicate-name handling, or what the created record contains.

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 short sentences, zero filler, with the core action front-loaded ahead of the scope exclusions. The exclusion list is slightly list-heavy for a one-parameter tool but still earns its place as scope definition.

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?

An output schema exists, so return values need no explanation, and annotations carry the safety profile. For a trivial single-required-parameter create tool the description is nearly sufficient, though it omits duplicate-handling and permission prerequisites.

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 0% for the single 'name' parameter, which has only minLength/maxLength constraints and no textual description. The description does not mention the name argument at all, so it fails to compensate for the coverage gap; only the obviousness of a single 'name' field keeps this above a 1.

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?

States a specific verb and resource ('Create a business'), and the exclusion list ('does not add cases, approved replies, refunds, replacements, or timelines') scopes it against related entities. It does not name the sibling list_businesses, so differentiation is by negative scope rather than explicit contrast.

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?

'When the user asks for one' gives a clear trigger condition, and the second sentence supplies when-not guidance by enumerating entities this tool must not create. No alternative tool is named, so the agent must infer that list_businesses handles reads.

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