Get Company By Id

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

The only behavioral detail disclosed is the credit cost. With no annotations present, the description carries full responsibility for describing side effects, read-only behavior, rate limits, or return behavior, but it provides none of that context.

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 text is short but under-specified rather than usefully concise. The cost note is a legitimate single piece of information, but a tool description should also convey purpose and behavior; this one does not.

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?

With no output schema and no annotations, the description needed to explain what is returned and under what circumstances this tool is appropriate. Instead, it provides only a cost notice, leaving the agent without enough context to safely and correctly invoke the 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 fully describes the single company_id parameter and includes an example value, so the schema does the necessary work. The description adds no semantic value about the parameter beyond what is already structured.

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 says only '1 credit per call.' It does not state what the tool does, what resource it acts on, or what operation it performs. The intended purpose must be guessed from the tool name, not from the description.

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 about when to use this tool versus alternatives such as get_company_by_url, get_company_by_domain, or search_companies. There are no conditions, prerequisites, or exclusions to help the agent choose correctly.

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