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

The description goes beyond the annotations by revealing the persistence and shared side effect: the saved profile is read by every other server. It also warns about usage frequency with 'Call it once, first,' which is meaningful given idempotentHint is false. It does not contradict any annotation.

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?

Three short sentences deliver the resource scope, the shared-profile side effect, and the sequencing rule. There is no filler, and the most decision-relevant fact ('call it once, first') is front-loaded at the end of a concise statement.

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 16-parameter mutation tool, the schema fully documents parameters, and the description adds the critical context: shared persistence, broad impact, and call ordering. With no output schema, a return-value description is not necessary for correct invocation. Nothing an agent needs to call this tool correctly is missing.

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 each parameter already has a clear description, so the baseline is 3. The description enumerates categories of fields but adds no parameter-level meaning beyond the schema, which carries the full semantic load here.

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 states a specific verb ('Set') and resource ('business profile'), plus the fields it covers: name, address, VAT id, bank details, and defaults. 'The ONE business profile for the whole suite' clearly distinguishes it from the client and invoice sibling tools, which work on different resources.

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 gives explicit guidance: 'Call it once, first.' It also explains why sequencing matters by stating that the profile is 'Saved to the shared profile every other server reads,' so an agent knows this should precede dependent operations. No alternatives are needed because no sibling tool covers business profile setup.

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