list_secrets

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

States 'Values are never returned', which is a key behavioral trait. No annotations provided, so description carries the burden. Does not cover permissions or rate limits, but adequately sets expectations for a simple read operation.

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?

Three sentences, no fluff. Essential information presented in logical order: what, then when, then parameter details.

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?

Adequate for a simple tool with one optional parameter and no output schema. Could mention return format of metadata, but not necessary. Good coverage of key aspects.

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?

Single parameter 'search' has 0% schema coverage. Description adds meaning: 'Filter by name (optional substring match)'. Clearly explains its purpose and behavior beyond schema type.

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?

Description clearly states verb 'list' and resource 'secret names and metadata' from VibOps vault. Distinguishes from siblings by specifying that values are never returned, and by naming create_secret as the alternative for storing.

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?

Explicitly states when to use (check credentials before jobs) and when not to (use create_secret for storing). Names alternative tool create_secret.

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