Analyze candidate vs JD gaps

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

Annotations already declare readOnlyHint=true, and the description does not contradict that. The description adds substantial behavioral detail about what the tool produces, including strategies, resume plan components, and candidate questions, which helps the agent predict the tool's behavior accurately.

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 long but information-dense and every major clause adds a distinct output category. It front-loads the core comparison and gap-strategy assignment before the resume-plan details, though bullet formatting would improve scannability.

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?

For a complex analysis tool with no output schema, the description is unusually thorough in enumerating return values: strategies, JD-to-evidence mapping, bridge projects, certifications, resume plan elements, and candidate questions. It falls slightly short by not addressing how optional parameters like career_stage or years_of_experience influence the analysis.

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 exactly 50%, so the description must partially compensate. It clarifies that resume_text, linkedin_text, and additional_context are candidate inputs, but it does not explain company, job_title, career_stage, or years_of_experience, leaving those optional parameters undocumented.

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 opens with a specific verb and resource: 'Compares the candidate (resume, LinkedIn, extra context) to the JD.' It then enumerates distinctive outputs like gap strategies, bridge projects, resume plan, and candidate questions, which clearly separates this tool from siblings like score_resume or render_resume.

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 usage context is implied by the detailed description: use this when you need a full candidate-versus-JD gap analysis and actionable resume strategy. However, it never explicitly states when to choose this over siblings like analyze_job_description, suggest_bridge_projects, or score_resume, nor does it mention any exclusions or prerequisites.

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