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

With no annotations available, the description must carry the burden of explaining behavior such as read-only usage, return semantics, or request limitations. It adds only 'Billing per call: 1 Credits,' which does not illuminate behavior or side effects.

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 short but under-specified; the first sentence merely duplicates the title, and the billing line is the only piece of useful non-duplicative information. This is brevity without substance.

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?

The tool has no output schema and no annotations, yet the description does not say what company details are returned, how the domain is used, or what happens when no input is provided. This leaves significant ambiguity for an agent.

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?

The input schema fully documents the sole parameter company_domain as 'Website / domain name,' so the description need not add much. The description contributes no additional param semantics, but the high schema coverage justifies the baseline score.

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 restates the tool name/title as 'Company Details' and adds only a billing note. It does not provide a concrete verb or explain what company details are obtained, nor does it distinguish itself beyond saying 'Group: Companies.'

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 is provided for when to use this tool versus sibling tools like website analytics or app detail tools. The description lacks any scenario-based direction or exclusions.

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