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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so safety is covered; the description adds the substantive behavioural detail that the payload is the company's profile/preferences as rendered on documents. Because there is no output schema, listing the returned fields (name, address, tax/bank, VAT rate, payment terms) is genuine added value. It does not discuss freshness or whether settings can be empty/unconfigured, which keeps it off a 5.

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?

A single front-loaded sentence that names the resource and then lists contents in priority order, followed by a two-word safety note. The trailing 'Read only.' is redundant with readOnlyHint=true, a small but real waste.

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 zero-argument, annotation-covered read tool with no output schema, the description supplies enough: what domain it covers and what fields come back. Missing only edge-case behaviour (empty settings, currency/locale of the VAT rate) that an agent might want before relying on the values.

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 tool takes zero parameters, so the schema carries no semantics to supplement and the baseline applies. The description correctly spends no space on parameters and instead characterises the returned content.

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?

Names a specific resource (company settings) and enumerates the exact contents: company name, address, tax and bank details, VAT rate, payment terms. That is far more than a restatement of the title. It stops short of differentiating itself from near-neighbours like fetchBillingContext or fetchCustomerContext, which an agent could plausibly confuse with 'tax and bank details'.

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 phrase 'used on documents' implies when this context is relevant (filling in quote/invoice headers), but there is no explicit when-to-use rule and no exclusion pointing to a sibling such as fetchBillingContext. An agent can infer the situation but must guess between overlapping 'context' tools.

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