search_resumes_by_name

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

No annotations are provided, so the description carries the burden of disclosing behavior. It states the search is case-insensitive and returns minimal identity fields, but does not explicitly confirm read-only nature, rate limits, or what happens with no results. For a search tool, this is adequate but not fully transparent.

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 concise sentences with no filler. The first sentence states the purpose and key constraint, the second lists return fields. Information is front-loaded and efficiently presented.

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 tool's simplicity (1 param, output schema exists), the description covers the key aspects: purpose, return fields, and downstream usage. Minor gaps like pagination or default limits are not critical. It adequately differentiates from siblings and works with the output schema.

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 input schema covers the parameter description well (case-insensitive name fragment). The description adds that it searches by first or last name, but this is already implied. With 100% schema coverage, baseline 3 is appropriate.

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 clearly states 'Find resumes by person name (first or last name)', specifying the verb and resource. It distinguishes this tool from siblings like search_resumes_by_skill and search_resumes by focusing on name search, and explains the minimal return fields, which aids the agent in understanding the tool's scope.

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 advises using the returned id with other tools to fetch full details, indicating a workflow. However, it does not explicitly state when to use this tool over siblings like search_resumes (which may search by other criteria) or when not to use it.

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