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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered without description help. The description adds one useful piece of content context — that names are returned alongside codes, i.e. it is self-contained for lookups — but says nothing about ordering, whether the full chart is returned, or how paging interacts with results.

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?

Two short sentences, front-loaded with the resource and its contents. The trailing 'SOAP GetNominalCodes' is protocol detail of marginal value to an agent, but it costs only a few tokens.

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 paginated read with no output schema, the description should at least sketch the returned fields; it says only 'codes with their names' and omits whether an internal ID or account type is included. Combined with missing ordering/total-count behaviour, this is adequate but not complete.

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%: both limit and offset are documented with defaults and maxima in the schema itself. The description contributes nothing about parameters, which is acceptable at this coverage level but earns only the baseline.

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 names the resource precisely ('the chart of accounts: nominal codes with their names'), which is unambiguous and clearly distinct from every sibling (customers, invoices, VAT rates, bank accounts). It stops short of a clean verb+resource statement in the sentence itself, relying on the title 'List nominal codes', but an agent can still tell exactly what data comes back.

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?

There is no when-to-use guidance, no mention of what nominal codes are used for (e.g. mapping transactions or invoice line items to accounts), and no routing to or away from any sibling tool. The agent must infer the usage context entirely.

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