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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description adds genuinely new behavioral context beyond that: this call never triggers an upstream provider refresh, which tells the agent results may be stale/cache-dependent and the call is cheap — though it stops short of saying what happens on a cache miss or what the payload looks like.

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, no filler, with the capability statement front-loaded and the key constraint immediately after. Nothing is wasted.

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 single-parameter read tool with full read-only annotations and no output schema, the description covers what is returned (classes, locations, tracking options) and the no-refresh constraint. The only real gap is silence on the provider argument and on result ordering/emptiness, which is minor at this complexity.

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 0%, and the description never mentions the single required 'input' object or its 'provider' field. The only saving grace is the enum listing three provider values in the schema, which an agent can read directly; the description itself contributes nothing to parameter meaning.

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 verb ('Read') and the exact resource contents ('cached classes, locations and tracking options'), which is far better than the tautological title 'Saved tracking dimensions'. It does not explicitly contrast with the closest sibling list_cached_gl_accounts, but the resource scope is distinct enough for an agent to choose correctly.

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?

'Never refreshes the provider' implies the cached-data use case, but there is no explicit when-to-use, no prerequisites, and no named alternative for when fresh provider data is needed. Usage must be inferred from a single negative clause.

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