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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true, so the safety profile is covered. The description adds value beyond them by disclosing the return payload (id, name, type Web/Form, active flag, title, member and referral offers, share/widget URLs) and the underlying GET endpoint, though it says nothing about pagination ceilings or rate limits.

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?

Three tight sentences with zero filler: capability first, then the downstream usage hint, then the endpoint. The field enumeration is dense but every item tells the agent what it will get back.

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 usefully enumerates the returned fields, and annotations plus a fully documented schema cover safety and pagination. The only remaining gap is explicit routing versus the get_program sibling for single-record reads.

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% with full detail on count, offset and program, so the schema already does the heavy lifting. The description only echoes the id/name filtering idea and adds no format or syntax detail beyond the schema, making baseline 3 appropriate.

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 ('List the referral programs in the account') and enumerates the fields returned, plus the backing endpoint GET /api/programs. It is distinguishable from the singular referralrock_get_program by the 'List' framing, but the description never names that sibling explicitly, so differentiation is inferred 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?

Gives a concrete downstream usage rule: 'Use the ids (or names) to filter members, referrals and rewards,' which tells the agent why to call this first in a workflow. It does not state when to prefer this over referralrock_get_program for a single program, nor any prerequisites/exclusions.

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