search_secrets

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

No annotations provided, so description carries full burden. It discloses case-insensitive regex and allowlist filtering, but does not specify return format (names vs. full secrets), behavior on no match, or error handling.

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?

Single sentence front-loading the action and key constraints (regex, case insensitive, allowlist filter). No extraneous words.

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?

For a simple one-param tool with no output schema and no annotations, the description is mostly adequate. However, it lacks details on return values and error behavior, which would be helpful for an agent.

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% (no description for 'pattern'). Description adds that it is a regex pattern and case insensitive, which provides essential semantic meaning beyond the schema's raw 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?

Clearly states the verb 'Search', resource 'secret names', and method 'by regex pattern (case insensitive)'. It distinguishes from siblings like 'list_secrets' by specifying a regex search, and 'get_secret' by targeting names only.

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?

Implied usage: use when needing to find secret names matching a pattern. No explicit mention of when not to use or alternatives among siblings like 'list_secrets' or 'get_secret'.

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