Analyze master resume

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

With no annotations, the description carries full burden. It discloses that it parses, builds a draft, and returns missing fields, and explicitly states 'Nothing is invented' – a transparency guarantee. It does not mention side effects or full return format, but for a read-like operation this is adequate.

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, no wasted words, with the core action front-loaded. The 'Nothing is invented' note is a valuable behavioral guarantee in minimal space.

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 zero-parameter tool with no output schema, the description explains what it does and its key output (missing fields). It implicitly relies on the stored resume without explicitly stating the prerequisite, but the workflow context from siblings covers that.

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?

Tool has zero parameters, so baseline is 4. Description adds no parameter-specific info as none exist, which is appropriate.

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 action: parse the stored master resume, build a draft Master Profile, and return missing fields. It distinguishes itself from siblings like upload_master_resume (which uploads) and get_user_profile (which retrieves existing profile) by focusing on analysis and drafting.

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 the tool is used after a resume has been uploaded and when a draft profile needs to be built. It does not explicitly name alternatives or exclusions, but the context is clear enough for an agent to determine its use case. Sibling context reinforces the workflow.

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