list_data_keys

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

No annotations are provided, so the description carries the burden. It states 'List all data keys' but the schema includes limit/offset, implying pagination and a default cap of 100, which is not disclosed. It also does not specify that it is read-only or describe the return format, leaving behavioral traits ambiguous.

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, front-loaded sentence with zero fluff. It conveys the essential action and resource without unnecessary detail, making it highly scannable.

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 no output schema, the description does not explain return values, but the parenthetical clarifies the resource concept. For a simple list tool with only pagination params, this is minimally adequate, though it lacks information about data key structure or any access criteria.

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% for both limit and offset parameters, so the schema fully explains their semantics. The description adds no parameter-specific detail beyond the parenthetical clarification of what data keys are, which is unrelated to params.

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 a specific verb ('List') with a clear resource ('data keys') and clarifies the domain ('custom key-value targeting variables'). This distinguishes it from sibling tools like get_data_key (single item) and list_data_key_targets (different resource).

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?

Usage context is implied by the name and description—use to enumerate all data keys, vs. get_data_key for a specific one—but no explicit guidance or alternatives are provided. The description does not mention when to use this over related list operations or mention pagination when many keys exist.

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