cases-update

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

With no annotations, the description bears the full burden of behavioral disclosure. It only states the action without revealing side effects (e.g., parent case changes affecting hierarchy), authorization needs, or constraints (e.g., immutability of certain fields). The verb 'updates' implies mutation but adds no further transparency.

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 a single sentence, concise and to the point. It covers the essential information without fluff, though it could be expanded slightly without losing conciseness.

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 absence of annotations and output schema, and the moderate complexity (especially the parent case field), the description is incomplete. It omits prerequisites (e.g., valid case_id), behavior when fields are omitted, response format, and potential constraints like read-only cases. A more complete description would address these 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?

The input schema provides 100% coverage with descriptions for all four parameters, including details like maxLength for name, special handling for description (empty string to clear), and the effect of parent_case_id. The description adds little beyond listing the fields, so it meets the baseline but doesn't enhance understanding.

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 tool updates a case and lists the specific fields that can be updated (name, description, parent case). It uses a specific verb and resource, distinguishing it from sibling tools like cases-update_status or cases-create.

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 provides no guidance on when to use this tool versus alternatives such as cases-create (for new cases) or cases-update_status (for status changes). No prerequisites or context are given for when an update is appropriate.

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