mosaic_competitive_landscape

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

Annotations already mark it as read-only and idempotent. The description adds value by explaining the multi-hop traversal and the specific data points (companies, patent counts, compound counts, competitive intensity). However, it does not disclose potential limitations like data recency or coverage scope.

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 concise with four lines, front-loading the main purpose. The multi-hop traversal detail is helpful. Could be slightly more structured by explicitly listing the parameter, but overall efficient.

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 availability of an output schema, the description adequately covers the tool's function and key outputs. It explains the multi-hop nature and competitive intensity. Minor gap: no mention of input parameter, but that is covered in the schema.

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%, but the description does not mention the single required parameter (gene_symbol). The agent must rely solely on the schema for parameter meaning. The description adds no semantic value beyond what the schema's description provides.

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 'Get the full competitive landscape for a drug target' with a specific verb and resource. It distinguishes from sibling tools by detailing multi-hop traversal and specific outputs (companies, patents, compounds, intensity).

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 explicit guidance on when to use this tool vs. alternatives like mosaic_get_target_patents or mosaic_org_portfolio. The description implies a broad competitive view but does not set usage boundaries or exclusions.

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