delimit_secret_list

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

No annotations provided. Description states 'Side effects: read-only. Calls ai.secrets_broker.list_secrets' and emphasizes it never returns values. Provides good behavioral context beyond the bare minimum, though lacks audit/permission details.

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?

Highly concise with bolded sections and bullet points. Every sentence adds value. No wasted words. Efficiently structured to convey purpose, usage, and behavior.

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?

Tool has no parameters and an output schema. Description specifies return type: Dict with key 'secrets' containing list of metadata records, plus next_steps suggestions. Completely covers all necessary information.

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?

Input schema has zero parameters (schema coverage 100%). Description explicitly states 'Args: None.' which adds no further meaning beyond the schema, meeting baseline expectation for no parameters.

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 'List secrets in the broker (metadata only — never values)' with specific verb (list) and resource (secrets). Distinguishes from siblings delimit_secret_get and delimit_secret_store.

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?

Explicit when-to-use ('inventory what credentials are stored without exposing values'), when-NOT-to-use (retrieve value -> delimit_secret_get, add one -> delimit_secret_store), and sibling contrast with delimit_secret_get.

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