kaiten_list_custom_properties

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is fully covered. The description adds a workflow hint about inspecting type/multi_select/data before assignment, which is useful, but says nothing about pagination behavior, result limits, or ordering. Reasonable but not rich beyond the 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?

Two short, front-loaded sentences with no filler; the purpose comes first and the advisory second. It is efficient, though the second sentence is slightly oblique about which fields belong to which context.

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?

An output schema exists, so return values need not be explained. But with three undocumented parameters and a paginated list tool, the definition leaves an agent without the filtering/paging information needed to use it well, and it omits the distinction from kaiten_get_custom_property.

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?

All three parameters (limit, query, offset) have 0% schema description coverage, and the description mentions none of them. Since the schema itself documents nothing, the description was the only place to explain what 'query' searches over or how offset/limit paginate, and it does not.

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 resource: 'Find existing custom property definitions.' An agent can tell this is a listing/retrieval tool for custom property definitions in Kaiten. However, it does not distinguish itself from the sibling kaiten_get_custom_property, so the list-vs-single retrieval split has to be inferred from the names.

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?

'Inspect type, multi_select and data before assigning values' gives a real usage context, implying this is a prerequisite to kaiten_set_card_properties. But it never names that sibling, never states when to use kaiten_get_custom_property instead, and gives no guidance on paging or filtering through results.

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