get_company_insights_premium

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

With no annotations, the description discloses important traits: credit cost and a failure policy ('If the request fails, you don't pay'). This adds value beyond basic functionality. However, it lacks details on auth requirements or rate limits.

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?

Two sentences fully cover purpose and cost/failure policy. No redundant information. Front-loaded with the main action.

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?

For a single-parameter tool with no output schema, the description is largely complete. It explains the combined data retrieval and cost/risk. Minor gap: it doesn't define 'Insight Details' vs 'Company Details', but the tool name suggests the scope.

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% (parameter 'username' with example 'amazon'). The description adds no additional meaning beyond the schema. Baseline 3 is appropriate as the schema already does the work.

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?

Description clearly states verb 'Get' and resource 'Company Insight Details & Company Details', indicating combined retrieval. However, it does not explicitly distinguish from similar sibling tools like 'get_company_details' or 'get_company_details_by_id', though 'in a single request' hints at efficiency.

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 mentions '5 credit per call', implying cost considerations, but provides no explicit guidance on when to use this tool versus alternatives (e.g., for simpler needs use 'get_company_details'). No when-not-to-use or alternative naming is given.

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