resume_tailor

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It does disclose membership requirements and the 35-credit cost, which is useful, but it does not state whether the original resume is modified, what the output format is, or any other side effects or limitations.

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 compact and front-loaded, with membership and cost stated immediately. Every phrase contributes meaning, and there is no redundant filler.

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 tool with two plain-text string parameters, the schema handles input documentation well and the description covers purpose, cost, and membership. However, with no output schema, the description does not state the return format, and it does not clarify how this differs from the sibling resume_rewrite 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 100%, with both resumeText and jdText clearly documented as plain-text resume and JD content. The description adds no additional parameter-level detail beyond restating the general purpose.

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's function: tailoring a resume to a target job JD and highlighting matching keywords and experiences. It is specific and understandable, though it does not explicitly differentiate itself from the sibling tool resume_rewrite.

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 use case is implied: use this when you have a target position JD and want a customized resume. However, there is no explicit guidance on when not to use it or how it compares to alternatives like resume_rewrite or resume_diagnose.

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