list_secrets

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

No annotations provided, so description must explain behavior. It covers pagination (limit, after), output storage as object ID, and return format. It does not mention authentication or rate limits, but adds useful context beyond schema.

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 somewhat verbose, including docstring-style comments and multiple sentences about object store integration. It is front-loaded with purpose but could be shorter.

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?

No output schema, but description explains return format (list of secrets or error, object ID). Covers pagination and object store integration. For a simple list tool with two parameters, it is fairly 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 coverage is 0%, so description fully explains both parameters: limit maximum count, after cursor for pagination. This adds meaning beyond the schema's type and default.

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 lists all secrets in the organization and provides names and IDs. It implicitly differentiates from the sibling 'get_secret' which retrieves a single secret.

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 says it's useful for getting an overview before retrieving specific secrets, implying a prerequisite or ordering. It explains output storage and reference, but does not explicitly contrast with alternatives or state when not to use.

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