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

With no annotations provided, the description must disclose behavioral traits. It only states 'Get a company's full drug/diagnostic portfolio' but does not mention whether the operation is read-only, what data is returned (e.g., pipeline includes preclinical? approved?), or if any side effects occur. The lack of detail limits transparency.

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, efficient sentence that gets straight to the point. However, it is so brief that it omits potentially useful context, which would not harm length. It earns a high score for lack of redundancy but could be slightly more informative without losing conciseness.

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?

Given the tool's simplicity (one parameter, output schema exists), the description is minimally adequate. The output schema likely provides structure, but the description does not clarify the scope of 'full portfolio' (e.g., including diagnostics? all phases?). This ambiguity slightly lowers completeness.

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 100% (one parameter with a clear example). The tool description adds no extra meaning beyond the schema's own description of 'company_name.' Per the scoring rule, a baseline of 3 is appropriate when coverage is high and description doesn't enhance it.

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 verb and resource: 'Get a company's full drug/diagnostic portfolio.' It is specific and distinct from sibling tools like 'find_by_phase' or 'find_by_target' which focus on more granular queries. The name also reinforces the purpose.

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?

No guidance on when to use this tool vs alternatives (e.g., when to use 'search_nodes' or 'get_coverage'). The description lacks any context about prerequisites, exclusions, or typical use cases, leaving the agent to infer solely from the command name.

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