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

Annotations already declare readOnly, non-destructive, and closed-world, and the description goes beyond them by naming the required scope ('Needs applications:read') and the exact error behavior ('another founder's application answers not_found'). It also discloses computed semantics an agent could not guess, such as reviewComplete ignoring optional empty questions and draft being null unless a job is queued or running. Rate limits and caching are unmentioned, keeping it short of a 5.

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?

The purpose is front-loaded in one short sentence, which is good, but the remainder collapses into a single sprawling block of semicolon-separated clauses with deeply nested parentheses that is hard to parse on first read. Given there is no output schema, most of the content earns its place, but sub-headings or bullets for the json and md sections would materially improve scanability.

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 must define the return shape and it does so thoroughly for both formats, including field-level detail (status, applyUrl, deadline, questions, progress, draft, form) and the md document's getfund:doc / getfund:q / getfund:end scaffolding. A single-application tool needs little more; only the applicationId's origin and format remain unexplained.

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 full burden and largely meets it: format json vs md is spelled out in terms of what each returns, and locale is tied to concrete effects ('url ... in locale' for json; 'its own words and gap hints in locale' for md). The applicationId parameter is only implied by 'One application' and never described as a UUID or how to obtain it, which leaves one of three parameters underspecified.

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 opening line 'One application with what its review needs' plus the format-specific breakdown makes clear this is a single-application read oriented at reviewing answers, which separates it in spirit from siblings like getfund_submission_answers and getfund_documents. It never states the retrieval verb explicitly or names an alternative sibling, so the differentiation is inferable rather than stated.

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?

The description does explain the fork between the two formats: json is the structured record, md is the review document as Notion-flavored Markdown, which implicitly tells the agent when to pick each. It gives no guidance on when to call this versus sibling tools such as getfund_submission_status or getfund_brain, and does not name getfund_me or the programs tools as prerequisites for obtaining an applicationId.

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