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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so safety is largely covered structurally. The description adds a useful behavioral nuance on top: 'It reads no user data,' which tells the agent no user context, auth scope, or privacy considerations are involved — beyond what the readOnly hint alone conveys.

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 sentences, front-loaded with the action and enumerated contents, then immediately followed by when-to-use and the no-user-data caveat. Every clause earns its place with no filler.

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?

An output schema exists, so return structure need not be explained; the description instead summarizes the semantic content of the response and confirms it touches no user data. For a zero-parameter, read-only informational tool this covers everything an agent needs to invoke it correctly.

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 baseline is 4 per the rubric. The description correctly implies a parameterless, context-free call and adds no misleading parameter claims.

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 and resource ('Return a factual overview of SavedThat') and enumerates exactly what the payload covers: service function, supported platforms, plan limits and prices, and links to apps and docs. This is clearly distinguishable from the sibling get_public_transcript, which deals with transcripts of user content rather than static product facts.

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?

Provides clear usage context: 'Use it to answer questions about the product itself.' That tells the agent when the tool is appropriate. It stops short of naming get_public_transcript as the alternative or stating an explicit when-not condition (e.g. for user-specific data), so it is strong but not fully routing.

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