sirr_key_list

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

No annotations provided, so description carries full burden. Critically discloses that 'Key values are never returned,' a key security behavior. Implies read-only operation via 'List,' though could explicitly state it is non-destructive.

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?

Two sentences, zero waste. First sentence states purpose; second sentence provides critical behavioral constraint. Efficiently front-loaded with no filler.

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?

Appropriate for a zero-parameter list operation. Covers the essential security constraint (key values omitted). Without output schema, could mention that metadata (IDs, creation dates) is returned, but sufficient 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?

Zero parameters per input schema (empty properties object). Baseline score applies as there are no parameters requiring semantic explanation beyond 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?

States specific verb (List), resource (API keys), and scope (for the current principal). Clearly distinguishes from siblings sirr_create_key, sirr_delete_key, and list_secrets by specifying operation type and 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?

Provides implicit guidance through 'Key values are never returned,' indicating when NOT to use it (when key values are needed). However, lacks explicit when-to-use guidance or mention of alternatives like sirr_create_key for generating new keys.

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