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

The description openly states the consequence of setting the description: it affects classification and dashboard tailoring. This, combined with readOnlyHint=false and destructiveHint=false, gives a full picture of the tool's impact without contradicting annotations.

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 two sentences long, direct, and free of unnecessary detail. It front-loads the primary action and follows with the purpose, making it efficient and easy to parse.

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 setter operation, the description covers the action, its purpose, and its downstream effects. No output schema is needed, and the context is sufficient for an agent to use the tool 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 single parameter 'whatwedo' is fully described in the schema with a clear explanation of its content and purpose. The tool description also reinforces its meaning as the business's own description, providing complete semantic coverage.

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 sets the business's own description, with a specific verb and resource. It distinguishes itself from siblings like set_business_tag or update_business by focusing narrowly on the 'whatwedo' field.

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 explains why one would use this tool (to classify the business and tailor dashboard/defaults), giving clear context. It does not explicitly contrast with alternative tools like update_business, but the specific purpose is evident.

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