Company/Organization Lookup

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

Consistent with readOnlyHint = true. Discloses cost, credit consumption, data caching behavior, and the effect of force_refresh. All behavioral traits are transparently described.

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?

Concise at about 5 sentences, front-loaded with purpose, then usage, then return format. Every sentence adds value without redundancy.

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?

Covers purpose, parameters, return structure (company, asn), cost, alternatives, and caching. No missing information for this simple 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?

Adds context beyond the schema, e.g., 'ip omitted means caller IP' and explains force_refresh behavior. Schema already describes both parameters well, but the description provides useful additional usage detail.

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?

Clearly states 'Read-only ownership lookup via GET /v3/ipgeo' and specifies the limited scope to company and ASN ownership, distinguishing it from the sibling lookup_ip which returns more fields.

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?

Explicitly mentions 'Paid only. Cost: 1 credit' and explains when to use force_refresh. Contrasts with lookup_ip, providing guidance on when to choose this tool over alternatives.

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