list_custom_property_select_values

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

Annotations already establish this as a safe, idempotent, open-world read, so the safety profile is covered. The description adds only the word 'paginated', which is useful but does not explain how pagination must be driven (cursors, previous_page fingerprinting) despite the schema exposing several cursor parameters for that purpose.

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?

A single front-loaded sentence with no filler, which is efficient. It is arguably under-specified rather than bloated, but as written every word earns its place.

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 described. However, for a 10-parameter tool with nested cursor objects and only 30% schema coverage, the description omits everything an agent needs to drive the paginated search correctly, leaving it inadequate for the tool's complexity.

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 only 30% against 10 parameters, so the description would need to compensate and it does not mention a single parameter. Filters like query, ids, order_by, detail, and limit are left entirely to the schema, along with the intricate offset/cursor parameters.

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?

States a specific verb ('Read') and resource ('select options of a custom property') and notes the underlying mechanism ('paginated v2 select search'). It distinguishes itself reasonably from the sibling list_custom_properties, which lists properties rather than a property's select options, though it does not explicitly name that sibling.

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 when-to-use guidance, no prerequisites (e.g. that a valid property_id is required), and no alternatives named. The need to look up select values is only implied by the resource name.

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