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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the description does not need to restate those. It adds useful context by noting the return is 'metadata' and that results are 'paginated,' and it scopes the operation to 'a Growth project.' This meaningfully supplements the structured annotations without contradicting them.

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 description is a single sentence with no filler. It front-loads the verb 'Read,' then names the resource, the pagination behavior, and the scope. Every word contributes meaning, and there is no redundant restating of the tool name or annotations.

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 read-only paginated list endpoint, the description covers the resource type, the scope, and the pagination behavior. The output schema handles return-value details, and the annotations cover the safety profile. Nothing essential for an agent to select and invoke this tool correctly is missing.

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 some parameter responsibility. It maps project_id via 'in a Growth project' and suggests limit/offset through 'paginated,' but it does not explain the individual parameters or their semantics. The schema's titles, defaults, and min/max constraints are reasonably self-explanatory, which mitigates the gap.

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 opens with a specific verb, 'Read,' and names a precise resource: 'paginated SAFE investment metadata in a Growth project.' This clearly separates it from sibling tools such as sparkclose.get_investment and sparkclose.list_scenarios, and the title 'List SparkClose investments' aligns with the description without being a mere tautology.

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 'paginated' wording and the 'list' title imply a bulk-read use case, which is useful context. However, the description never explicitly states when to prefer this tool over sparkclose.get_investment for a single investment, or over sparkclose.list_scenarios for scenario data. Usage guidance is only implied, not stated.

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