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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered; 'No business data is changed' merely reinforces that. The one substantive addition is the note that the post lives under a feed and returns the same field selection as the list tool, but the shape of that selection and the not-found behavior are left undisclosed.

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?

Four short sentences, front-loaded with the action and key, zero filler. 'No business data is changed' is slightly redundant against readOnlyHint but is a cheap safety affirmation.

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 should describe the return more concretely than 'the same selected fields as the corresponding list tool', and it says nothing about behavior when the post or feed does not exist. Adequate for a simple two-parameter read, but with clear gaps.

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%, so the description bears the burden. It does distinguish the two parameters by role ('one feed post by its Givecloud ID' vs 'a known feed_id') and correctly flags feed_id as required, but it never clarifies which identifier the post's own `id` is nor gives format guidance beyond the regex pattern.

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 feed post') plus the lookup key, and contrasts scope with the list counterpart ('Returns the same selected fields as the corresponding list tool'). An agent can distinguish it from givecloud_list_posts without opening a schema, though the sibling is referenced generically rather than named.

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?

'A known feed_id is required' implies this is a second-step call after discovering a feed, but the description never states the when-to-use rule explicitly or names givecloud_list_posts as the way to obtain the ID. Usage is inferable rather than stated.

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