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

With annotations present, the bar is lower, and the description still contributes real context: it discloses the return shape ('the link, not a summary'), the coverage limitation ('only covers releases still in the feed' – so stale meetings vanish), and the credit cost. It does not say what happens when a requested meeting is no longer in the feed, which is the one notable gap.

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 what the tool returns, then the use case, then the caveat and cost. Nothing is redundant; the parenthetical cost note is compact and earns its place.

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-optional-parameter read tool with no output schema, the description carries the return-value burden well (link, meeting, release date) and flags the feed-coverage limit. Only the empty/absent-meeting behavior is left unspecified, which is a minor omission for a tool this simple.

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?

Annotations (readOnly, idempotent, openWorld, not destructive) already establish the safety profile, and the description adds genuinely useful behavior: link-only return, feed-limited coverage, and a 1-credit cost. Schema coverage is 100% and the single optional 'meeting' parameter with its YYYY-MM format and latest-default is fully documented there, so the description adds little about parameters beyond confirming that the latest is the default case.

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?

Specific verb and resource: it names the feed (the Board's monetary policy feed), the payload (meeting covered, release date, link), and explicitly draws a boundary by saying it 'Returns the link, not a summary of the minutes.' It stops short of naming the sibling it is not (e.g. fed_monetary_policy_releases for older releases or fomc_meeting_dates for the calendar), so differentiation is only partial.

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 real usage scenario ('are the Fed minutes out?' three weeks after each meeting) and a scope limit ('only covers releases still in the feed'), which implies when to reach elsewhere. It never explicitly says what to use for historical minutes or for the meeting calendar, so the guidance is implied rather than stated.

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