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

Annotations already declare destructiveHint=true and idempotentHint=true; the description adds real context beyond them — a sign-in requirement, the implicit upsert behavior when the same type and time are submitted twice, and immediate visibility on techjobs.vn. It never spells out which operations are the destructive ones (cancel, clear_fields), but the portmanteau of auth, dedup, and propagation notes is substantive.

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?

Four sentences, each carrying distinct information (auth, add payload, edit modes, dedup, propagation), with no filler. Slightly front-loaded on the sign-in caveat rather than the core action, and the parenthetical field list is dense, but nothing is redundant.

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 14-parameter mutation tool with no output schema, the description covers the create/edit duality, the dedup edge case, auth, and result visibility. It leaves unexplained what happens to unspecified fields on edit (the schema's 'omit to keep' convention carries that) and what a successful call returns, a minor gap.

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 the baseline is 3; the description still adds meaning by grouping the fields into an add-payload and by mapping interview_id to the edit modes (mark done/passed/failed, reschedule, cancel). That interpretation of the edit branch is not derivable from the enum descriptions alone.

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?

States a concrete verb and resource — adds an interview round to a tracked application, or edits an existing one when interview_id is supplied — and enumerates the payload (type, date/time, format, link, interviewers, prep notes). This clearly separates it from list_interviews (read) and save_interview_retro (retrospective), so an agent can route without inspecting the schema.

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?

Gives a clear create-vs-edit rule (omit interview_id to add, supply it to edit) and names the sibling that produces that id ("id from list_interviews"). It also describes the dedup rule for repeated type+time. It stops short of an explicit 'use X instead' routing statement against save_interview_retro or update_application.

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