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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description is not needed for that. It does add real value beyond the annotations by disclosing the shape of the returned record (offers, agent-tool capabilities, decision-maker, exclusions, sources, date checked) and by hedging with "where reviewed," signalling that some fields may be absent.

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?

One front-loaded sentence with no preamble or filler; the field enumeration is the only bulk and it earns its place by describing the payload. Slightly list-heavy but efficient.

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 output schema, the description must carry return-shape information and it does reasonably well, listing the record's contents and the 'where reviewed' caveat. It omits behavior on an unresolvable or unknown id, which is the main remaining gap for a lookup tool.

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 100%, and the single id parameter is already well documented with examples ("aws.activate-credits", "aws-activate-credits", link, exact name). The description adds nothing about the identifier, so baseline 3 applies.

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?

Names a specific verb and resource ("Returns one program's reviewed record") and enumerates the content of that record, so the agent knows this is a single-record read rather than a list operation. It never explicitly names search_programs as the many-record sibling, so differentiation is implied by "one program" rather than stated.

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?

Usage is only implied: the singular framing plus the id parameter suggest 'use this once you have an identifier.' There is no explicit guidance on how to obtain an id (e.g., search_programs first) and no mention of alternatives such as compare_programs or what happens if the id is unknown.

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