get_customers

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

No annotations are provided, so the description carries the burden. It discloses that results come from SEC 10-K filings and include citation evidence, which is good. However, it does not mention potential limitations like data recency, pagination, or read-only behavior.

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 three sentences plus an example, all front-loaded. Every sentence adds value: purpose, source, evidence, example. No unnecessary words.

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 simplicity (one parameter, no output schema, no annotations), the description is largely complete. It explains the output (customers with citation evidence) and the data source. Could mention limitations like only covering SEC filings, but overall sufficient.

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 schema coverage is 0%, meaning the description does not explicitly describe the parameter 'ticker'. The example shows usage with 'TSM', implying it is a stock ticker, but no formal definition is given. The description should compensate by explicitly stating the parameter meaning.

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 'Get all known customers of a company' which is a specific verb+resource. It elaborates on the source (SEC 10-K filings) and provides an example. This clearly distinguishes it from sibling tools like get_competitors and get_supply_chain.

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 explicit when-to-use or when-not-to-use guidance is given. However, the purpose is clear enough that an agent can infer when to use it for customer relationships. Alternatives like get_competitors are not mentioned, but the tool name provides distinction.

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