draft_complete_application

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

Description discloses automatic PDF generation and conditional email template creation based on email presence, but lacks details on side effects (file overwriting, default output path), error handling, or return behavior. No annotations provided to supplement.

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 sentences efficiently convey purpose and key behavior (PDF generation, conditional email). Front-loaded with the main action. Could benefit from a brief usage hint but remains concise.

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 5 parameters (2 required), nested objects, no output schema, and 16 sibling tools, the description lacks completeness: no mention of return values, success/failure indicators, file naming conventions, or scenarios where email is missing. Leaves agent uncertain about outcomes.

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 60%, so parameters are partially documented in schema. The description adds minimal parameter-specific insight beyond 'email address is found,' not clarifying which schema field triggers email generation. No explanation of complex nested object usage.

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?

Description clearly states the tool drafts a complete application package (CV, cover letter, email template) and specifies outputs (PDFs). It distinguishes from siblings that generate individual components, though 'complete' implies comprehensiveness; however, no explicit differentiation from similar tools like generate_cv_pdf.

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 on when to use this tool vs. individual siblings (e.g., generate_cv, generate_cover_letter). The description assumes the user wants a full package; no mention of scenarios where only partial generation is needed or prerequisites.

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