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

The description discloses important behavior beyond the readOnlyHint annotation, especially that it returns metadata only and never the secret value. It also makes clear the assistant cannot create or set secrets, which is consistent with the annotations and adds useful safety context.

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 concise and front-loaded, leading with the core purpose before adding contextual details. Every sentence contributes either to what the tool does, how it fits into the workflow, or an important limitation.

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 list operation with a fully described input schema and an existing output schema, the description provides sufficient context: scope, return-value limitation, usage scenario, and fallback action. No critical gaps remain for an agent deciding to call this tool.

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?

The input schema already provides full descriptions for all three parameters, so the description adds little parameter-specific information. The surrounding text gives useful context for slug-based filtering, but it does not meaningfully extend the parameter semantics 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?

The description opens with the specific action 'List the secrets' and clearly identifies the resource and scope (authenticated tenant). It distinguishes itself from related tools by emphasizing metadata-only access and explicitly stating that secrets cannot be created or set through the assistant.

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?

It explicitly says when to use the tool: to discover which secret slugs exist for wiring an api template's auth.secret. It also provides a when-not case by directing users to the dashboard when the secret does not exist and stating that creation is not possible through the assistant.

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