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

Annotations already cover read-only and non-destructive status, yet the description adds substantial behavior: the auth requirement ('Needs tracker:read and the Autopilot plan'), page-size bounds, cursor semantics with null on the last page, default sort ordering per scope, exclusion of past deadlines in open scope, omission of empty fields, and locale-driven summary/url. This is well beyond what the structured fields convey.

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 content is front-loaded and nearly every clause carries information, but it is delivered as one dense semicolon-chained paragraph mixing scope, sort, filters, pagination and auth, which makes it harder to scan than a short structured breakdown would 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?

For a 10-parameter, no-output-schema listing tool it conveys the essential contract: what each scope returns, ordering rules, pagination with total, filter behavior and auth requirements. The only meaningful omission is the role of startupId, which an agent must guess at.

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 mostly delivers: it explains scope, sort, type, country syntax ('one code or a comma list such as TR,US'), q's search fields, closesWithinDays, limit range and cursor/total page semantics. Two gaps remain — startupId is never mentioned, and the cursor parameter is described under the name 'nextCursor', which could mislead an agent about which field to pass.

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+resource ('Programs a page at a time, with the details a table needs') and enumerates the returned fields per scope, so an agent knows this is a paginated program listing tool. It does not, however, distinguish itself from the sibling getfund_search_programs, which an agent could easily confuse with this filtered listing.

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 explicit context for choosing between the two modes: scope matches for the startup's matched programs, scope open for the whole open catalog, with a clear statement that open scope drops past deadlines. What it lacks is any comparison to sibling tools such as getfund_search_programs, so tool selection at the top level is left to inference.

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