get_company_details

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

No annotations are provided, so the description should disclose behavioral traits like read-only nature, permissions, rate limits, or response structure. The description only says 'enrich', which is unclear, and fails to clarify that this is a read operation or any safety profile.

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 sentence, which is concise, but it is grammatically awkward ('The endpoint enrich...') and lacks structure. It could be improved for clarity without adding length.

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 abundance of sibling tools and the absence of an output schema, the description should provide more context about the nature of the returned 'full details' and how this tool fits into the overall API. It is insufficiently complete for an agent to correctly select and invoke this tool.

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 has 100% description coverage with a simple example, but the tool description does not add meaning beyond the schema. The parameter 'username' is not explained further, and the description does not clarify what kind of identifier 'username' is (e.g., company LinkedIn username) or how it relates to other tools accepting domain or ID.

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 states the tool 'enrich full details of the company', giving a general idea of returning comprehensive information, but the verb 'enrich' is vague and the purpose is not clearly specified compared to sibling tools like 'get_company_employees_count' or 'get_company_insights_premium'.

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 provides no guidance on when to use this tool versus alternatives. With multiple company-related tools (e.g., by domain, by ID), there is no indication of the appropriate context for using 'username'.

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