publish_business

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

With no annotations, the description must carry the full burden of behavioral disclosure. It only says 'creates or updates' without detailing side effects, required permissions, whether updates are partial or full replacements, or error handling. This is insufficient for a mutation tool of this complexity.

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 immediately states the tool's purpose and key fields, with no wasted words. It is appropriately sized for a CRUD tool with schema support.

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?

The description provides only the basic create/update action without guidance on usage context, expected outputs, or update semantics. With 17 parameters and no annotations or output schema, the description is insufficient to fully understand the tool's behavior in context.

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 covers 88% of parameters with descriptions, so the description does not need to compensate for missing parameter documentation. It merely lists a few field names that are already described in the schema, adding no new meaning. This meets the baseline but does not go beyond it.

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 creates or updates a business/local commerce in Rovee, listing key fields like name, category, address, contact, schedule, and images. This specific verb+resource combination distinguishes it from sibling publish tools for blog posts, POIs, events, and guides.

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 creating or updating businesses but does not provide explicit guidance on when to choose this tool over others like publish_poi or publish_event. It lacks any mention of alternatives, exclusions, or prerequisites, so the usage context is only implied.

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