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

Annotations already declare idempotentHint=true, destructiveHint=false, and readOnlyHint=false, so the safety profile is supplied structurally. The description adds useful behavior (status vocabulary, default status 'applied', tracker destination), but omits the note-replacement semantics of the notes field and the applied_at defaulting behavior.

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 core action and destination, then packs status semantics efficiently. The status list is slightly redundant with the schema enum but earns its place by framing the saved/applied distinction; nothing is wasted.

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 7-param, zero-required mutation tool with no output schema, the description covers the primary decision points (which status, which input form) adequately. It would be fully complete if it clarified note-replacement and the interaction with update_application.

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 only 57%, so the description meaningfully compensates by explaining the status enum's intent and the mutually exclusive job-vs-(title+company+apply_url) input mode. It does not explain notes replacement or the applied_at default, leaving a couple of gaps.

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 specific verb+resource ('Add a role to the user's JustBacked tracker ... or update its status') and even names the visible surface (justbacked.com/saved). However, it does not differentiate itself from the sibling update_application, which also changes application status, leaving a potential ambiguity an agent must resolve by inference.

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 concrete conditional guidance for status choice ('saved' for considering, 'applied' only after confirmation) and explains the alternate input path for externally-found roles (title + company + apply_url instead of job). It stops short of naming when to prefer update_application or add_to_list over this tool.

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