update_candidate

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

Discloses that arrays (tags, skills, social_urls) are replaced rather than merged. No annotations provided, so description carries burden. Lacks details on permissions or side effects but 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 with no wasted words. Purpose is front-loaded. Highly concise and structured.

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?

Covers essential update behavior and return value. With 12 parameters and nested objects, the description is adequate but could mention validation or error handling. No output schema, but description explains return.

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 coverage is 100%, so baseline is 3. Description adds value by noting 'only send fields you want to change' and clarifying that certain arrays replace existing values, which goes beyond 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?

Description clearly states 'Update an existing candidate's profile' with a specific verb and resource. It distinguishes from siblings like 'create_candidate' and 'get_candidate'.

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?

States that all fields are optional for partial updates and returns the updated object. Provides clear context for when to use, though could explicitly mention not to use for creation.

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