search_agents

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. The one-liner only restates the tool's function without explaining return format, result limits, permission requirements, or how the search matches agents—significant gaps for an agent.

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 concise sentence with no fluff, making it front-loaded and efficient. However, it is so sparse that it borders on under-specification, though this is more a completeness issue than a conciseness one.

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 lack of annotations, output schema, and parameter descriptions, the description is incomplete. It doesn't clarify search scope, return values, or constraints. With many sibling tools in the context, more guidance is needed to avoid misuse.

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 schema has one required parameter 'query' with no description and 0% coverage. The description adds no meaning beyond the parameter name, leaving the agent to guess what the query should contain (e.g., name, email, other attributes). It fails to compensate for the schema's lack of detail.

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 uses the specific verb 'search' and identifies the resource 'agents in Freshdesk', making the core purpose clear. However, it doesn't explicitly differentiate from sibling tools like 'get_agents' (list all agents) or 'view_agent' (retrieve a specific agent), relying on the inherent meaning of 'search'.

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 provides no guidance on when to use this tool versus alternatives such as 'get_agents' or 'view_agent'. It doesn't mention search syntax, query requirements, or any exclusions, leaving the agent without context for selecting the appropriate tool.

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