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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false), so the bar is lower. The description still adds meaningful non-annotation context: the data is published/firm-authored material sourced from a specific URL, implying a static snapshot rather than live deal data or personalized guidance. It does not state staleness or freshness guarantees.

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 sentence that front-loads the verb and resource and then lists the returned content. No filler, no restatement of the title, nothing that fails to earn 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?

With no output schema, the description must carry the return-value burden, and it does so by enumerating the fields returned (ticket size, geography, stage, conviction, how to pitch). Combined with annotations covering safety and zero params, this is nearly complete; only freshness/staleness of the published data is left unstated.

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?

The tool takes zero parameters (empty object, additionalProperties=false), so per the rubric the baseline is 4. There is nothing for the description to disambiguate on the input side, and it does not confuse the reader with any implied optional inputs.

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+resource: 'Returns Mode VC's published investment parameters' followed by an explicit enumeration of the payload (ticket size, geography focus, stage, core conviction, how to pitch). An agent can immediately tell this is a firm-level thesis lookup. It does not explicitly contrast itself with get_investor_details or search_investors, so it stops short of a 5.

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?

Usage is only implied — the mention of 'how to pitch' hints at the fundraising/pitch-prep scenario, but there is no explicit when-to-use, when-not-to-use, or alternative routing (e.g. 'use get_investor_details for other firms, this only covers Mode VC'). Adequate but leaves the agent to infer the trigger condition.

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