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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so "No business data is changed" largely restates them. The useful addition is the disclosure that the return fields match the corresponding list tool, which tells the agent what shape of payload to expect.

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 short sentences, front-loaded with the core action and ID requirement. The safety sentence is somewhat redundant against the annotations but does not impede comprehension.

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 no output schema, the description covers what it does, what it returns (same fields as the list tool), and its safety profile. Only not-found behavior and how to source the ID are left unstated.

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 0% — the only structured hint is the name `id` and a regex pattern. The description adds that the ID is a Givecloud ID and that it identifies a single contribution, but it does not explain the ID format or where an agent would obtain one.

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 with explicit scope: "Read one contribution by its Givecloud ID." The singular "one contribution" plus the reference to the corresponding list tool lets an agent distinguish this from givecloud_list_contributions without opening either schema.

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 by the contrast between "one contribution" and the referenced list tool, but there is no explicit instruction such as 'use this when you already have the ID, otherwise use givecloud_list_contributions.' No prerequisites or exclusions are stated.

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