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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the mutation aspect is covered. The description adds context about the settings affected (rounding, signatory, company info), which is useful. However, it does not disclose overwrite behavior, required permissions, or side effects beyond what annotations provide.

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 front-loaded sentence with no wasted words. The parenthetical adds concrete detail efficiently, making it one of the most concise yet informative descriptions among typical tools.

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?

This is a complex tool with 18 parameters, 13 required, and no output schema. The description only provides a high-level summary and does not explain required fields, save semantics, or what response to expect. An agent cannot reliably invoke this tool correctly without additional information beyond the sparse schema.

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 only 11% (only client_id and rounding_off have descriptions). The description names broad categories but fails to explain key required parameters like weighted_equity_shares, weighted_potential_equity_shares_py, or the distinction between unit_label and unit_divisor. With 18 parameters, the description does not compensate for the low schema 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 uses a specific verb ('Save') and resource ('statement settings') and lists concrete categories ('rounding unit, signatory details, company information used on the statement face'). This distinguishes it from sibling save tools such as save_accounting_policies or save_disclosures, which target 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 implies usage for saving statement-specific settings but provides no explicit when-to-use guidance, prerequisites, or comparison with alternatives like save_accounting_policies or save_share_capital. There are many save_* sibling tools, so an agent would need more direction.

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