find_company

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

No annotations are provided, so the description must carry the behavioral load. It discloses the key output (company_id) and its downstream use, which is genuinely useful, but says nothing about matching semantics (partial vs exact name), result limits, whether multiple companies can be returned, or permission requirements.

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?

Two tight sentences plus a worked example, with the purpose front-loaded before the chaining guidance. The example earns its place by showing the exact parameter handoff, though it is slightly redundant with the preceding sentence.

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?

Since an output schema exists, return values needn't be described in prose, and the description still adds the crucial link between company_id and search_tickets. For a one-parameter lookup tool this is nearly sufficient, with only matching behavior left unspecified.

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% for the single 'query' parameter, so the description has to compensate. The example ('query=Defence') implies the query is a company name and that partial names work, but there is no explicit statement of matching rules or format.

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?

States a specific verb+resource ('Search Freshdesk companies by name') and clearly distinguishes itself from siblings like find_agent and find_requester, which resolve other entity types. It also names the output artifact (company_id), so an agent knows exactly what this tool produces.

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?

The description gives a concrete workflow: run find_company, then feed the returned company_id into search_tickets to get tickets for that organisation. That is clear usage context, though it stops short of stating when this is preferable to other lookup paths or any exclusion conditions.

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