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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false. The description adds meaningful context beyond those by explicitly stating 'Discovery never authorizes spending' and 'No wallet or account required,' which reassures agents about side effects and prerequisites.

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 with no filler. The core action is front-loaded, and each additional sentence adds distinct value: one addresses authorization safety, the other addresses access prerequisites.

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 parameterless read-only tool with strong annotations, the description fully covers what an agent needs to know: it is a safe, free, account-less discovery operation. No output schema exists, but the simple nature of the tool does not demand more.

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 has zero parameters and the schema coverage is 100%, so there is no parameter meaning for the description to add. Per the baseline for zero-parameter tools, this is effectively complete.

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 'Read free optional tip terms,' a specific verb plus resource that clearly identifies the tool as a read-only lookup. It is easily distinguished from siblings like prepare_tip_quote and get_tip_receipt, which imply quote preparation and receipt retrieval.

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 clear context: this is for discovery only, never authorizes spending, and requires no wallet or account. It does not explicitly name sibling tools or say when not to use it, but the behavioral caveat effectively separates it from spending-related operations.

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