Search company data

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

Annotations already declare the tool as readOnly, idempotent, non-destructive, and openWorld. The description adds the HTTP method (GET) and authorization class (board_or_agent), which is helpful but minimal. It does not disclose error handling, rate limits, or pagination behavior. With annotations covering safety, the description adds moderate value.

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 short (three lines) and includes the endpoint and auth class. However, it is too minimal and omits essential information. Conciseness is good, but the lack of substance reduces its effectiveness.

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 tool's complexity (single parameter, read-only, but search functionality) and the presence of an output schema, the description is incomplete. It does not explain what data is being searched, how results are structured, or any search query capabilities. The context is insufficient for an agent to use the tool effectively.

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 description contains no information about parameters. The input schema has one parameter (path with companyId) but has 0% schema description coverage. The description fails to explain what companyId represents or how to format it, leaving the agent to infer from the name.

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 'Search company data' and the endpoint path indicates a search per company ID. However, it does not specify what kind of search (e.g., full-text, filtered) or differentiate from similar sibling tools like pc_get_companies_by_company_id or pc_get_companies_by_company_id_search_extract. The purpose is vaguely clear but lacks specificity.

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 on when to use this tool versus alternatives. There is no mention of when to use search vs. listing all companies or retrieving a single company. The description offers no context for tool selection.

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