chat_with_resume

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

The description discloses the two-step behavior (fetch resume then send message), which is useful context beyond the tool name. However, with no annotations, it does not mention whether the operation is read-only, how history is handled, or any 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?

Two concise sentences with no wasted words, front-loaded with the primary action.

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?

The description covers the core function and workflow. It does not explain the use of the optional history parameter, but the schema covers it. With no output schema, the description sufficiently conveys the tool's role.

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 input schema provides descriptions for all three parameters (resumeId, message, history) with 100% coverage. The tool description adds no additional parameter-specific meaning 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 tool's purpose: chatting about a resume, with the specific behavior of fetching resume content first. This distinguishes it from sibling tools like get_resume or tailor_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 description implies usage for resume-related chat but does not explicitly contrast with alternatives or state when not to use it. No exclusions are mentioned.

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