batch_parse_resumes

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

The description discloses that results are raw and the LLM must interpret them, adding behavioral context beyond the readOnlyHint annotation. It does not contradict annotations, and it clarifies that no mutation occurs.

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?

Three sentences with no redundancy: first defines action, second lists outputs, third instructs the LLM. Every sentence earns its place, and critical info is front-loaded.

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?

While there is no output schema, the description lists output components (raw text, pipeline analysis, etc.) and tells the LLM to interpret results. This provides sufficient context for an agent to handle the complex output, though more detail on pipeline behavior could improve completeness.

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% and already defines the files parameter with its subfields. The description does not add extra detail beyond the schema, meeting the baseline but not exceeding it.

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 the tool parses multiple resume files and runs a full algorithmic pipeline, which distinguishes it from parse_resume (singular). It specifies the resource (resumes) and action (batch parse), making the purpose unambiguous.

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 implies batch use for multiple files but provides no explicit guidance on when to choose this tool over siblings like parse_resume or analyze_resume_comprehensive. No when-not-to-use or alternative recommendations are given.

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