resume_parser

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

No annotations exist, so the description must fully disclose behavior. It states the output is structured JSON but does not explain error handling, input format validation, or the effect of the use_zoho_parser flag. The phrase 'Provide a base64-encoded PDF or raw text' is ambiguous about which parameter corresponds to which input and whether one or both must be supplied.

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, clearly front-loaded with the purpose. It contains no filler. However, the phrase 'Provide a base64-encoded PDF or raw text' could be more tightly integrated into parameter guidance, and the sentence structure is slightly awkward. Still, it is concise and wastes no 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 3 parameters (none required), 0% schema coverage, and an output schema (not described), the description is insufficient. It does not specify that at least one of resume_text or resume_base64 should be provided, nor does it explain the meaning of use_zoho_parser. The return value is partially indicated ('structured JSON with skills, experience...') but no details about the output schema shape. This leaves an agent likely to misuse the 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 description coverage is 0%, so the description must compensate. It adds meaning by indicating that input can be base64-encoded PDF or raw text, which correlates to the two string parameters. However, it does not clarify that resume_text and resume_base64 are alternatives, nor does it explain the use_zoho_parser boolean. The description adds some value but leaves key semantics unexplained.

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 a resume into structured JSON, listing the extracted fields (skills, experience, companies, education, projects). It uses a specific verb ('Parse') and resource ('resume'), and is distinct from all sibling tools which focus on candidate/job management rather than document parsing.

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 is provided on when to use this tool vs alternatives, nor any conditions or prerequisites. The description does not mention that the tool expects either resume_text or resume_base64, nor when to set use_zoho_parser to true. Given the sibling tools include candidate_match_score which might also process resumes, the lack of comparative guidance is a gap.

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