Change the role I am looking for

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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description adds specific consequences beyond annotations: previous roles are removed, including a resume-derived role, and recommendations and title-less searches change accordingly. This is exactly the kind of destructive impact detail an agent needs.

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?

The purpose is front-loaded in the first sentence, followed by relevant destructive consequences and the sibling alternative. Every sentence conveys useful information with no redundant restatement of the tool name or title.

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?

Given one parameter, 100% schema coverage, rich annotations, and an output schema, the description supplies the remaining behavioral context an agent needs: what gets removed, how recommendations change, and when to use the alternative tool. Nothing essential is missing.

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 description coverage is 100%, so the parameter is already well documented in the schema, including where careerProfileId comes from. The description adds only a general reference to 'the one role the user chose' and does not meaningfully extend parameter semantics beyond the 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?

The description uses a specific verb and resource: it replaces the roles saved on the user's FoundRole account with one chosen role. It clearly distinguishes itself from the sibling profile_role_set by explaining that replace removes previous roles while set saves one for accounts with no role yet.

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?

It explicitly names the alternative profile_role_set and the condition that selects it: an account with no role yet. This gives the agent a clear when-to-use-this-vs-sibling rule.

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