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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description usefully discloses the scope of returned data (including 'every open role'), hinting at a potentially broad payload, but says nothing about freshness, rate limits, or behavior for unknown companies. Adequate but not rich.

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 efficient sentence with every clause carrying content; no wasted words. It loses a point for being a fragment that front-loads a bare noun phrase rather than an action, though the enumerated fields are informative.

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 carries the return-value burden and does so credibly by listing the profile fields. For a one-parameter read tool with annotations covering safety, the remaining gaps (pagination, data freshness, error handling) are minor.

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?

With 100% schema coverage, the single 'company' parameter is fully documented, including the accepted formats (company_slug or name). The description adds no further parameter meaning, so the baseline 3 for high-coverage schemas 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 enumerates the exact content of a startup profile (round, amount, investors, headcount, HQ, hiring velocity, open roles), making it clear this is a company-profile retrieval tool. It is a noun phrase rather than a verb phrase, and it does not explicitly differentiate itself from siblings like search_jobs or get_job, so it falls 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?

The description contains no guidance on when to use this tool, when not to, or which alternative to pick when the agent wants job-level or listing-level data. The only workflow hint ('company_slug from search_jobs') lives in the schema, not the description, so no usage guidance is provided here.

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