camelot_salary_negotiation_planner

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

Annotations already cover readOnly=false, idempotent=true, destructive=false; the description adds a meaningful non-annotated trait: 'Local browser processing.' This tells the agent that computation happens locally, which is useful privacy/processing context beyond the structured annotations. No contradiction with annotations.

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 description is short and front-loaded with the action verb, but it includes a redundant 'Salary Negotiation Planner:' prefix that repeats the tool name, and the trailing canonical URL is not useful for an AI agent. Slightly more efficient would be to remove the URL, but overall it is compact.

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 the tool has an output schema and 100% parameter documentation, the description does not need to explain return values or parameter formats. It provides a sufficient high-level overview plus the local-processing behavior. It does not cover usage context, but that is already penalized under usage_guidelines, and the tool is simple enough that this coverage is adequate.

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 all four parameters are already documented with clear descriptions. The tool description adds no parameter-level meaning beyond the schema, so the baseline 3 applies.

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 ('Prepare') plus resource ('compensation targets, supporting evidence, and negotiation talking points'), clearly stating what the tool produces. The name 'Salary Negotiation Planner' and the action make it distinct from siblings like camelot_interview_prep or camelot_offer_letter_generator, so an agent can differentiate it without opening schemas.

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?

The description implies usage through its action-oriented phrase ('Prepare compensation targets...') — an agent can infer it is for salary negotiation planning. However, it provides no explicit when-to-use, prerequisites, or alternatives, so it stops at implied usage rather than clear context or exclusions.

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