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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is covered structurally. The description adds provenance context (unsponsored, transparent sources, confidence ratings), but says nothing about freshness, coverage limits, or behavior on an unknown startup_id, which is the remaining gap.

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 first sentence is dense but front-loads the returned fields well. The second sentence ('Unsponsored vendor intelligence dossier with transparent sources and confidence ratings') largely restates the 'evidence-graded' and 'verified' framing already implied, adding promotional padding rather than new information.

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 usefully enumerates what the dossier contains, which is the key information an agent needs before calling. It is essentially complete for a single-id read tool, lacking only error/miss behavior for an invalid startup_id.

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?

There is a single parameter with 100% schema description coverage, and the schema already explains that startup_id comes from search_startups or get_ranking. The description adds no format, constraint, or sourcing detail beyond the schema, so baseline 3 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 names the resource (a startup dossier) and enumerates the returned content areas: problem, solution, stage, team, buyer-fit score, and verified enterprise customers. It is clearly distinct from search_startups or get_ranking by being a single-entity retrieval, though it never uses an explicit retrieval verb like 'fetch' or 'returns'.

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?

There is no statement of when to call this versus siblings such as search_startups, compare_vendors, or check_listing. The only routing hint ('from search_startups or get_ranking') lives in the parameter schema, not the description, so the description itself offers no usage guidance or exclusions.

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