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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds real value beyond that with the constraint that these preferences do not convert invoice amounts, pre-empting a plausible misuse, but it says nothing about what the returned profile contains.

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, both earning their place, with the resource named first and the crucial caveat front-loaded right after. Nothing to trim.

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 read-only tool with no output schema, the description covers purpose, scope and the main misinterpretation risk. Only the shape of the returned preferences and the no-argument input are left unstated.

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?

There are no meaningful parameters (a single required empty 'input' wrapper) and schema coverage is 0%. The description does not tell the agent that no arguments are needed, which is the one useful thing it could add about the input.

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?

States a specific read operation and names the exact resources: saved bookkeeping/document currency, locale and timezone preferences. It clearly is not one of the many invoice-mutation siblings, though it does not explicitly contrast with update_workspace_preferences.

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 word 'Read saved' implies this is the retrieval counterpart to update_workspace_preferences, and the caveat about not converting invoice amounts implies when not to rely on it. However, no sibling or condition is named explicitly, so the routing guidance remains inferred.

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