organization_search

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

No annotations exist, and the description fails to disclose any behavioral traits such as pagination behavior, rate limits, data freshness, or whether results are sorted. The link to external docs does not compensate for the lack of explicit information.

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 short (two sentences) and includes a helpful URL, but it lacks structure. The purpose is clear, but it does not front-load key information or use formatting to improve readability.

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 complexity of the input schema (many nested parameters) and no output schema, the description is insufficient. It does not explain what the search returns, how to interpret results, or any limitations. The link partially compensates but the description itself is incomplete.

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 description adds no value beyond the schema. Although the nested fields in the schema have detailed descriptions, the top-level 'query' parameter is undocumented in the description, and the description does not explain how to construct the query object.

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?

Description clearly states it is for finding organizations using an API endpoint. The sibling tool names (organization_enrichment, organization_job_postings, people_enrichment, people_search) help distinguish its purpose as a search 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?

No guidance provided on when to use this tool versus alternatives like organization_enrichment or people_search. The description does not mention any prerequisites, filters, or typical use cases.

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