update_chore_priority

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

No annotations provided, so description carries full burden. It discloses the priority scale meanings and that the tool returns the updated chore. However, it omits details like whether the action is destructive, reversible, or requires permissions. For a simple update, it is adequate but not thorough.

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?

Three sentences: action, usage guidance, and parameter details. No filler, front-loaded with the core purpose. Every sentence serves a distinct function.

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 simplicity (2 params, no output schema, no annotations), the description covers the core functionality and return value. It lacks error conditions or authentication notes, but is sufficient for a targeted update tool.

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?

Both parameters are described in the schema (100% coverage), but the tool description adds value by fully defining the priority scale (0=unset, 1=lowest, 2=low, 3=medium, 4=highest), which the schema only partially covers. This helps the agent select the correct value.

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 'Update' and the resource 'a chore's priority level (0-4)', distinguishing it from sibling tools like 'update_chore' and 'complete_chore' by specifying the exact parameter adjusted.

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 says 'Use this to adjust how urgent a chore is without editing other details', providing clear when-to-use guidance. It implies when not to use (if other fields need editing), but does not explicitly state alternatives, though the context is sufficient.

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