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

Annotations declare non-read-only, non-destructive, non-idempotent, but the description adds two things annotations cannot: the record is persisted "for the catalog review" and the call "Needs applications:write" scope. It does not say whether repeat reports are deduplicated or what is returned, which is the remaining 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?

A single dense sentence front-loads the purpose, then the issue kinds, then the identity arguments and permission requirement. Nothing is redundant, though the parenthetical inventory of fields makes it slightly harder to scan than a short bulleted structure would.

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 write tool with no output schema, it covers the trigger conditions, the identifying arguments, the destination of the record, and the required permission. Slightly incomplete on post-call behavior and on whether opportunityId or applicationId is mandatory in practice.

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 carries the burden and largely does: it explains that kind must be one of four named values, that note is free text, that suggestedUrl is optional, and that the target is given "by opportunityId or applicationId". It does not clarify that neither identifier is schema-required or what happens if neither is supplied.

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?

The description names a specific verb and resource ("Reports a wrong apply URL, a captcha or login wall, or another blocker on a program") and enumerates the exact issue kinds, so an agent can tell it apart from siblings like getfund_report_submitted or getfund_set_status without opening the 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?

It spells out the concrete situations that should trigger a report (wrong apply URL, captcha, login wall, other blocker) and the side effect (stored for catalog review), which is enough to decide when to call it. It stops short of naming an alternative tool or stating exclusions, so the when-not is only implied.

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