list_company_profiles

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

No annotations are supplied, so the description carries the full behavioral burden. 'available' suggests a read-only enumeration, but the description does not explicitly state read-only/non-destructive behavior, permission requirements, or ordering/pagination characteristics.

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?

It is a single short fragment with no wasted words, which keeps it concise. The fragmentary grammar makes it slightly less immediately actionable than a complete sentence, but there is no bloat.

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 parameters, has an output schema, and is a simple list operation, so the description does not need to explain return values. It establishes the resource and its link to match_profile, but leaves the exact invocation relationship and read-only nature implicit.

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 tool has zero parameters and schema coverage is 100%, so the baseline is 4. There are no parameter semantics for the description to add, and it does not introduce any misleading parameter information.

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 names the resource ('Names of the company profiles') and ties it to 'match_profile', but it is a noun phrase rather than a verb-led statement of what the tool does. It implies a name-list lookup but does not fully distinguish its purpose from the sibling match_profile tool.

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?

'available to match_profile' implies this is a precursor lookup for match_profile, but the description never explicitly says to call this before match_profile. It also gives no when-not-to-use guidance or alternatives, leaving usage only implied.

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