kaiten_list_select_values

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so safety is covered. The description adds real context that card values are arrays of numeric option IDs, useful for piping results into kaiten_set_card_properties, but it says nothing about pagination or that results are scoped to a single property.

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 the operation front-loaded and no filler. The second sentence is slightly tangential to invocation but is short enough not to hurt.

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?

With an output schema present, return values needn't be explained, but for a four-parameter tool with zero schema descriptions the omission of property_id, filtering and pagination context leaves the definition inadequate for correct invocation.

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% across four parameters, and the description supplies no parameter meaning whatsoever: property_id, query, limit and offset are all unaddressed. An agent must infer that property_id scopes the lookup and that query/limit/offset control searching and paging.

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 verb+resource ('Find existing select options') is identifiable, but the description never says these options belong to a custom property, which is the required parameter and the core of the tool's identity. It also gives no basis for distinguishing it from siblings like kaiten_list_catalog_values or kaiten_list_custom_properties.

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 statement of when to call this tool, no prerequisites, and no mention of alternatives such as listing custom properties or catalog values first. The second sentence describes how option IDs are consumed elsewhere rather than when to use this tool.

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