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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds the underlying endpoint (GET /api/program/getsingle) and the returned field set, but says nothing about exact-match failure behavior, case sensitivity, or permissions — meaningful gaps for a lookup that can miss.

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 terse fragments with zero padding, and the identifying scope ('by its exact name') is front-loaded ahead of the endpoint. The telegraphic style borders on under-specification but wastes nothing.

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 one-parameter read tool with full annotation coverage, the description is nearly sufficient, and it usefully compensates for the absent output schema by naming the returned fields. The only real omission is behavior on a missing or non-exact name.

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 coverage is 100%, so the single 'name' parameter is fully documented, including the cross-reference to referralrock_list_programs. The description's 'exact name' phrasing reinforces the exact-match semantics but adds little beyond what the schema already states.

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 ('One referral program by its exact name') and enumerates returned fields (id, active flag, offers, URLs), so the agent knows exactly what comes back. It implicitly distinguishes itself from referralrock_list_programs by emphasizing a single exact-match lookup, but never names the sibling tool.

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: fetching one program requires knowing its exact name, and the pointer to referralrock_list_programs for discovery lives in the schema's parameter description rather than the tool description. There is no explicit when-not-to-use guidance or statement of what happens on a failed name match.

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