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

Annotations already declare readOnlyHint=true and destructiveHint=false, so 'No business data is changed' largely restates that. The claim that it returns 'the same selected fields as the corresponding list tool' adds some useful context about return scope, but nothing is said about behavior for missing/invalid IDs, field selection, or auth.

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 the core action front-loaded; nothing is buried. The closing safety sentence is largely redundant with the annotations, which is the only wasted material.

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 single-parameter read tool with annotations covering the safety profile and no output schema, the description says enough to call it correctly. Remaining gaps (not-found behavior, which fields are selected) are minor at this complexity level.

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?

There is one parameter with 0% schema description coverage, so the description carries the burden. It clarifies that the input is a Givecloud ID (as opposed to an external or supporter ID), which is genuinely useful, but it does not describe the ID format or validate the pattern constraint.

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 ('Read one recurring profile by its Givecloud ID') and scopes it to a single record, which distinguishes it from the sibling list_recurring_profiles. It refers to 'the corresponding list tool' rather than naming it, so differentiation is clear but not maximally explicit.

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 implied: fetch one record when you already have its Givecloud ID. There is no explicit statement of when to prefer this over givecloud_list_recurring_profiles or how to obtain an ID when you don't have one, leaving the routing to inference.

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