workers_salary_confirm

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

With no annotations, the description fully discloses critical behaviors: the need for confirm=true, quote expiration, idempotency/conflict error, and a mutation constraint (cannot decrease contribution). The contact direction is also helpful.

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?

Extremely concise: three short sentences, each providing distinct value. Front-loaded with the core purpose. No wasted words.

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 presence of an output schema (not shown), the description covers input constraints, error scenarios, and mutation rules. It omits explanation of the 'group_id' parameter and success outcomes, but the output schema likely fills gaps.

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 0%, so description must compensate. It clarifies the 'confirm' parameter behavior. However, 'quote_id' (required) and 'group_id' are left unexplained, though 'quote_id' is partially inferred from the tool's purpose.

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 clearly states the verb 'Charge' and resource 'salary quote', distinguishing it from related tools like workers_salary_quote (quoting) and workers_tt_buy_confirm (different quote type). The mention of 'confirm must be true' further clarifies the action.

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?

Provides practical usage hints: quote lifespan (~5 min), reuse error (409), and a constraint on decreasing contribution. While it doesn't explicitly say 'use after workers_salary_quote', the context and sibling names make it clear. Lacks a direct 'when not to use' statement.

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