get_card_param_values

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

No annotations exist, so the description carries full burden. It only states the operation is a 'get' (read), but fails to disclose any behavioral traits such as error conditions, rate limits, or response format. The description is too minimal for safe autonomous invocation.

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 sentence, which is concise, but it sacrifices informativeness for brevity. It front-loads the core purpose but does not earn its place by adding value beyond the tool name.

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?

Given the lack of output schema and annotations, the description should provide more context about return values, potential errors, and how this tool relates to sibling tools like get_card_param_remapping or search_card_param_values. It is incomplete for effective tool selection and 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%, meaning the tool description adds no parameter semantics beyond the schema's property descriptions ('Card ID', 'Parameter key (slug)'). The description does not elaborate on the meaning or usage of the `id` and `param_key` parameters, leaving the agent to rely solely on the schema.

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 clearly states the tool retrieves possible values for a card filter parameter, using specific nouns ('card', 'filter parameter') and a verb ('get'). It distinguishes from related tools like get_card_param_remapping, but does not explicitly differentiate from search_card_param_values, so it gets a 4.

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 guidance is provided on when to use this tool versus alternatives like search_card_param_values or get_card_param_remapping. There are no prerequisites, exclusions, or context for effective use.

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