value_list

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

With no annotations provided, the description carries the full burden. It discloses filtering behavior and sorting order ('newest-first'), but omits details such as result limits, pagination, idempotency, or side effects. The behavioral context is adequate for a simple read operation but not comprehensive.

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 extremely concise: two sentences followed by a clearly formatted parameter list. Every sentence serves a purpose, and the structure is front-loaded with the tool's purpose. No wasted words.

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?

The description covers all parameters and sorting order. Given the presence of an output schema, return values need not be detailed. However, it does not mention potential result limits or pagination, which are common for list operations. Overall, it is nearly complete for a filtered list tool.

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?

The input schema has 0% description coverage, so the description fully compensates by explaining each parameter's meaning and allowed values (e.g., status options, source types, scope values, tag requirements, carried_by semantics). This adds significant value beyond the bare 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 'List values, optionally filtered,' which is a specific verb and resource. It distinguishes from siblings like value_read (single value retrieval) and value_add (creation), making it evident that this is for listing multiple values.

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 description does not provide explicit guidance on when to use this tool versus its siblings. While it describes the filters, it lacks statements like 'use this to get all matching values' or 'use value_read for a single value,' leaving the agent to infer usage context.

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