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

Goes well beyond the annotations: it discloses the default status, the free-account cap of 5 applications versus unlimited PRO, and — crucially — that supplying only jobUrl causes the server to fetch the page and that the fetched text must be treated as untrusted. That is prompt-injection-relevant context an agent could not infer from readOnlyHint/openWorldHint alone.

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?

Front-loads the action and the "at least a company or role" constraint before the conditional linkage rules and quota caveat. Every sentence carries information, though the dependency conditions (cvId/jobDescription, jobUrl-alone) read as slightly compressed clauses that could be cleaner as a short list.

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 6-parameter mutation with no output schema, the description covers creation defaults, input minimums, conditional fetch behavior, untrusted-content handling, and plan quotas. The one gap is the return value: it never hints what the caller gets back (e.g., a new application ID or the populated record), which matters for a create tool with no output schema.

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, but the description adds genuine cross-parameter semantics the schema only states piecemeal: cvId pairs with jobDescription, and jobUrl alone triggers page fetching and field population. The remaining parameters (locale, company, roleTitle) are left entirely to the schema, which is fine at full coverage.

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?

Opens with a specific verb and resource ("Add a job to the user's job application tracker") and pins down the resulting state (status "saved"). The verb "add" together with an explicit creation default distinguishes it from the sibling update_takemeup_application without needing to open either 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?

Explicitly names the trigger condition ("Use when the user saves or applies for a job") and states the minimum input requirement ("Give at least a company or role"). It does not explicitly route to update_takemeup_application for jobs already tracked, so the create-vs-update boundary is implied by the verb rather than stated.

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