search_applicants

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

No annotations, so description must cover behaviors. Mentions pagination and that q filters results, but doesn't disclose behavior when q is empty, search scope defaults, or performance implications. Missing critical details.

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?

Very concise at two sentences, front-loaded with purpose. Could include a bit more detail without being verbose.

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?

No output schema, so description should explain return format or behavior. Missing info on default behavior without q, interaction with status/vacancy filters, and search scope. Incomplete for a 7-parameter tool.

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 100%, so baseline 3. Description adds minimal nuance: 'q parameter actually filters results' and pagination details, but parameters are already well-described in schema.

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?

Clearly states 'Text search for applicants (name/email/resume)', specifying the verb and resource. Distinguishes from siblings like list_applicants by implying search vs list, but could be more explicit.

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 on when to use search_applicants vs list_applicants or other siblings. Mentions pagination but no context for appropriate use.

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