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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It implies a search/read operation but does not explicitly state read-only behavior, absence of side effects, rate limits, or any other operational traits. The description adds no behavioral context beyond the generic verb 'search'.

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 a single short sentence, but it is under-specified rather than appropriately concise. It lacks structure or front-loading of critical information; the sentence is so vague that it provides little value, making it closer to a placeholder than a useful definition.

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?

With three undocumented parameters, no output schema, and no annotations, the description is grossly inadequate. An agent cannot determine what arguments to pass, what the response will look like, or any constraints, making the tool effectively unusable based solely on this description.

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 coverage is 0%, and the description does not mention any of the three parameters (limit, query, item_type). An agent has no guidance on what these parameters mean, their format, or how they influence the search results, failing entirely to compensate for the schema's lack of descriptions.

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 a verb 'search' and a resource 'reviewed public demand or offers', but 'reviewed' is ambiguous and the resource doesn't clearly map to the tool name 'find_counterparty'. It does not differentiate from sibling tools like discover_commercial_counterparties, making the purpose unclear and only weakly indicative of what the tool actually does.

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?

There is no guidance on when to use this tool versus alternatives. Sibling tools such as publish_demand, publish_offer, and discover_commercial_counterparties exist for related operations, but the description provides no conditions, exclusions, or scenarios for choosing this tool.

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