validate_resume

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

No annotations are provided, so the description carries the full burden. It discloses the checks performed (identity, fabrication count, etc.) but does not describe the output format, error behavior, or whether the tool is read-only. 'Validate' suggests a safe operation, but more detail would improve transparency.

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 sentence that efficiently conveys the purpose and key checks. It is front-loaded with the verb and resource, with no wasted words.

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 a simple tool with one parameter and no output schema, the description adequately explains what the tool does but omits the return value (e.g., success/failure, list of issues). This gap in behavioral completeness lowers the score from a potential 4.

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 covers 'json_path' as 'Path to tailored JSON file' (100% coverage), meeting the baseline of 3. The description adds value by clarifying that the file is a 'tailored resume JSON' and that validation is against the 'base resume', providing context beyond the 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?

The description clearly states the action ('validate'), the object ('tailored resume JSON'), and specifies what it checks ('identity, fabrication count max 10, bullet count guardrails, hedging phrases'). It distinguishes itself from sibling tools like 'save_tailored_resume' or 'get_base_resume' by focusing on validation.

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 validation should occur after tailoring a resume, but it does not explicitly state when to use this tool versus alternatives like 'get_tailoring_rules' or 'save_tailored_resume'. No exclusions or when-not-to-use guidance is provided.

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