kaiten_list_catalog_values

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered. The description's one piece of added behavior is that the returned ID must be stringified when set on card properties, which is a non-obvious integration detail worth credit, but it says nothing about pagination behavior or what a catalog value actually represents.

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 sentences with no filler, though the second sentence is usage advice rather than purpose and would be better framed as such. Structurally front-loaded with the action.

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 needn't be spelled out, but for a four-parameter, zero-coverage list tool the description leaves too much unexplained: what a catalog is in Kaiten, how it relates to custom properties and select values, and how pagination works. The required property_id and its role are never stated.

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 0% and all four parameters (property_id, query, limit, offset) are undocumented in the schema. The description compensates only indirectly by implying property scoping; it never explains that query is a filter, that limit/offset paginate results, or that property_id is required.

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?

"Find existing catalog values" names a verb and a resource, so the basic read intent is graspable, but "catalog values" is never defined and the description never distinguishes this tool from the many sibling list tools (kaiten_list_select_values, kaiten_list_custom_directory_records, kaiten_list_custom_properties). An agent cannot tell from this text which list tool retrieves which kind of value.

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 second sentence hints at downstream usage (assign the returned value ID as a string in card properties), which is genuinely useful, but there is no statement of when to call this versus the near-identical sibling list tools, and no prerequisites beyond the implicit property scoping.

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