Resolve the venture and market

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

Annotations already indicate read-only, but the description adds valuable behavioral constraints (never submit secrets/confidential evidence) and clarifies it handles ambiguous names. Adds context beyond annotations without contradiction.

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 somewhat repetitive with repeated 'Use when' phrasing, but it's concise overall and front-loaded with the core purpose. The labels 'Use when' and 'Do not use when' improve scannability.

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?

Covers usage context, exclusions, and data confidentiality. An output schema exists, so return values don't need description. Minor gap: no mention of failure behavior, but not essential.

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 coverage is 100% with descriptive property texts, so the description doesn't need to add parameter details. It adds no extra semantic value beyond the schema, but the baseline applies.

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 clearly states the tool resolves entities (startup, venture, etc.) to country, sector, and archetype before evidence assessment. It explicitly differentiates from siblings by positioning it after mvr_first_call and before readiness assessment.

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?

Provides explicit 'Use when' and 'Do not use when' conditions, including sequencing after mvr_first_call and exclusions for readiness verdicts. Names an alternative context and gives clear boundaries.

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