Extract company search matches

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

The description states it is a GET operation with 'Authorization class: board_or_agent', which is consistent with the annotations (readOnlyHint=true, destructiveHint=false, idempotentHint=true). It does not contradict annotations but adds minimal behavioral context beyond what annotations already indicate.

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 very concise, consisting of two short sentences with no redundant content. However, it could include more useful information without becoming verbose, so it scores well but not perfectly.

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 description lacks important context such as the relationship to search operations, what the output contains (despite an output schema being present), and prerequisites. This leaves significant gaps for an agent to use the tool correctly.

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?

Schema description coverage is 0%, and the description does not mention the `companyId` parameter at all. The parameter name is self-explanatory, but the description adds no meaning or constraints, leaving the agent to infer the parameter's role from the tool name alone.

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 restates the title 'Extract company search matches' without elaborating on what exactly 'search matches' are or how this differs from sibling tools like `pc_get_companies_by_company_id_search`. The purpose is implied but not clearly specified, and no distinction from alternatives is provided.

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 on when to use this tool versus alternatives such as `pc_get_companies_by_company_id_search` or `pc_get_companies_by_company_id`. The description only provides the HTTP endpoint and authorization class, leaving the agent without context for invocation.

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