kaiten_update_custom_property

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

With no annotations, the description is the only source of behavioral disclosure, and it provides none beyond the action already implied by the tool name. It does not mention partial vs full update, side effects, permissions, or constraints like the one-per-company formula progress property documented in the schema.

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 no filler. However, it is under-specified to the point of being only slightly more informative than a restatement of the tool name.

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?

This is a 12-parameter mutation tool with nested objects, no output schema, and no annotations, yet the description offers no usage context, no field semantics, no mutation behavior, and no alternative routing. The definition is far from complete for an agent selecting and invoking the 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?

Schema description coverage is 100%, so the schema already documents all 12 parameters. The description itself adds no parameter context, but the high coverage means the schema carries the semantic load, which warrants the baseline score.

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 and concrete resource ('custom property'), and the update action distinguishes it from sibling create/get/delete operations. It does not add scope or expected effect, but an agent can infer the basic operation.

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?

There is no guidance on when to update a custom property, what prerequisites exist, or how this differs from create_custom_property/delete_custom_property. The only hint is the verb 'update,' which is not enough to choose between overlapping operations.

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