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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so safety is covered. The description adds valuable behavioral context: it lists the exact information returned (mode, approval state, per-product estimates, pooled example price, progress, recent changes) and states the credential requirement 'Last Price credential with routing read scope'. It does not mention rate limits or error conditions.

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 front-loaded with the core purpose, but the bulk is a single run-on sentence that lists many return fields in a dense, comma-separated clause. It is not repetitive, but the structure would be clearer as separate sentences or a bulleted list. The length is justified by the number of return aspects covered, but readability suffers.

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?

With no parameters and no output schema, the description carries the burden of explaining what the tool returns. It does so thoroughly, covering settings, estimates, progress, and recent changes. The credential requirement is also stated. The only minor gap is the lack of explicit error conditions or pagination behavior, but these are not central for a zero-parameter read.

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 no parameters, so the baseline is 4. There are no parameter semantics to clarify, and the description correctly does not waste words on inputs.

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 opens with a specific verb and resource: 'Read learned pricing for your workspace'. It then enumerates the exact information returned, making the tool's purpose unmistakable. However, it does not explicitly differentiate itself from close siblings like get_learned_elasticity_curve or list_learned_price_changes.

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 provides no guidance on when to use this tool versus alternatives, nor does it state any exclusions or prerequisites beyond a credential requirement. The only contextual note is that estimates are included 'also while learning is off, as a preview', which describes behavior rather than usage.

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