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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description earns credit for what it adds: the ordering semantics of the returned list and the explicit auth scope ('Needs tracker:read'). It omits paging/truncation behavior even though a limit parameter exists, which keeps 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?

It is front-loaded with the core purpose and contains no filler, but the single run-on sentence stacks parentheticals, a pipe-delimited enum list, and a nested colon clause, which makes the field-level details harder to scan than they need to be.

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, describing opportunity.applyUrl, linkStatus, searchHint and applyMode is genuinely necessary and well done. However, for a three-parameter filtered list tool, the absence of any filtering or pagination explanation leaves a real gap in what an agent needs to call it correctly.

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% and the three parameters (q, limit, startupId) are entirely undocumented. The description spends its words on output fields instead, so an agent gets no signal on what q matches, what limit defaults to, or whether startupId is required to scope results.

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 concrete resource and scope: 'The programs still to apply to', with an explicit ordering (upcoming deadlines, undated, expired/delisted last). That is clearly distinguishable from catalog-style siblings like getfund_programs or getfund_search_programs, though it never names an alternative explicitly.

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 gives strong downstream workflow guidance ('with account_required or captcha do not attempt the form, hand the program off to the founder in one sentence'), but says nothing about when to call this versus getfund_programs, getfund_application, or getfund_queue_add. Usage is implied by the 'still to apply to' framing rather than stated.

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