list_custom_property_select_values

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does state 'read-only,' which is a useful safety hint, but it does not mention error behavior (e.g., what happens for invalid property_id), return format, or pagination. For a simple list operation this is adequate but not richly transparent.

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 a single, concise sentence that front-loads the key information (verb, resource, and read-only nature). There is no wasted wording, and it is easy to parse at a glance.

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 simple, one-parameter list tool with no output schema, the description is adequately complete. It clearly states the operation and the parameter's purpose. The only minor gap is lack of explicit mention of the return format (a list of values), but that is strongly implied by the verb 'List' and the tool name. The read-only note adds useful context.

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 parameter property_id is already described as 'Custom property ID (select/catalog type)'. The description adds no additional meaning about the parameter, leaving it to the schema, which is sufficient. Baseline 3 is appropriate.

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 the specific verb 'List' with a clear resource: 'select/catalog values of a custom property'. This distinguishes it from sibling tools like list_custom_properties (which lists properties) and get_custom_property (which retrieves a single property), leaving no ambiguity about what this tool returns.

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?

No explicit guidance is given about when to use this tool versus alternatives. The purpose is obvious from the name and description (retrieve the enum values of a specific custom property), but there is no stated context or exclusions, such as 'use only for select-type properties' or 'use list_custom_properties to find property IDs first.'

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