List Custom Properties

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive behavior. The description adds meaningful context beyond those hints: the endpoint, the global scope, and the meaning of the `type` field when constructing kaiten_update_card.properties payloads. No contradiction with annotations.

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 front-loaded with the core purpose and stays compact. Each sentence earns its place: the first gives the action and scope, the second explains why the returned type field matters for writing, and the third gives the exact endpoint.

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?

For a read-only list tool with one optional parameter, the description is largely complete. It explains scope, endpoint, and how the returned type field affects later writes, though it does not enumerate the exact response fields beyond `type`.

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 only parameter, verbosity, is fully covered by the input schema with an enum, default value, and short description. The tool description adds no additional parameter-level guidance, which is acceptable because schema coverage is 100%.

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 action ('List') and the resource ('company-wide custom property definitions (custom fields)'), and it clarifies the global scope. It is unambiguous about what the tool returns, though it does not explicitly contrast itself with the similar sibling kaiten_list_custom_property_select_values.

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?

It gives useful context by explaining that custom properties are global per company/workspace, not per space, which tells an agent not to call this per space. It also implies this should be consulted before writing card properties via kaiten_update_card, but it does not explicitly state when-not-to-use or name alternatives.

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