List license keys

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is fully covered. The description adds only 'paginated', which is useful but thin; it doesn't disclose default/max page size (that lives in the schema) or how pagination should be traversed.

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 zero filler or repetition. It is appropriately sized for what it attempts to convey.

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 nine optional filter parameters and no output schema, the description should ideally explain the return shape or how filters combine, but it does not. Annotations and the rich schema cover much of the load, leaving this minimally adequate rather than complete.

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 89%, so the nine filter parameters are already well documented in the schema, and the baseline for high coverage is 3. The description adds no parameter meaning beyond what the schema provides, but it doesn't need to compensate for a gap.

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 states a clear verb (returns/list) and resource (license keys), so an agent knows the basic operation. However, it is essentially the title restated plus the word 'paginated', and it offers no differentiation from siblings such as list_license_key_instances or get_license_key.

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 when-to-use guidance is given: nothing explains when to prefer this over list_license_key_instances or get_license_key, and no prerequisites or filtering conditions are mentioned. The agent is left to infer everything from the name.

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