Update Business Profile

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

No annotations are provided, so the description carries the full burden of explaining behavior. It does not disclose whether updates overwrite existing values, if any validation occurs, whether changes are reversible, or what the return response looks like. This is a significant gap for a mutation tool.

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 only two sentences long and front-loads the core action ('Update a field on the business profile') before giving usage context. Every word earns its place, with no redundancy.

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 two-parameter tool with full schema coverage, the description is adequate but not rich. It omits behavioral details such as error behavior, permission requirements, or confirmation, and there is no output schema to fill in return-value expectations. Still, the basic update purpose is clear enough for minimal use.

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 both parameters fully (100% coverage) with an enum for 'field' and a type description for 'value.' The description adds example fields in prose but does not add semantic meaning beyond the schema, so the baseline 3 applies.

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 opens with 'Update a field on the business profile,' which is a specific verb+resource phrasing that clearly states the tool's function. It distinguishes this tool from siblings like view_profile (read-only) and setup_business (initial setup) by focusing on updating an existing profile.

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 explicitly says 'Use this when you get new information like your Business Number, GST registration, or payroll details,' providing clear usage context. However, it does not mention when not to use it or name alternative tools, so it stops short of full explicit guidance.

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