kadam_adv_update_autorule

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

Annotations only provide readOnlyHint=false. The description reveals a key behavioral trait: 'read-modify-write' and 'full payload is rebuilt from current state', adding value beyond annotations. However, it omits potential side effects or race conditions.

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, concise sentence with no wasted words. It front-loads the purpose and packs behavioral guidance efficiently.

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?

The tool has 12 parameters with enums and no output schema, yet the description omits return values, error handling, and prerequisites. For a complex mutation tool, this is insufficient for complete agent understanding.

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?

With 42% schema description coverage, the description explains the partial-update strategy but adds no per-parameter details beyond what the schema provides. It clarifies optionality but does not compensate fully for undocumented params like conditions or action.

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 'Update an autorule', specifying the verb and resource. It adds the 'read-modify-write' pattern, distinguishing it from create, delete, and status-only tools among siblings.

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 hints at partial updates ('pass only the fields to change') but does not explicitly contrast with alternatives like kadam_adv_set_autorule_status or kadam_adv_create_autorule. Usage context is implied, not directly stated.

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