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

Adds essential behavior beyond the readOnly/non-destructive annotations: the value is never returned, value_preview is only a non-sensitive hint such as trailing characters, and secret values cannot be set through this assistant. These are exactly the constraints an agent needs to avoid misusing the tool.

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?

Two sentences, front-loaded with the core lookup behavior, followed by the critical limitation and the redirect to the dashboard. There is no wasted text.

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?

Complete for a metadata-only getter: the input schema covers both lookup parameters, annotations cover safety, and an output schema exists. The description fills the critical gap by explaining that secret values are never returned and cannot be modified here.

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 100%, and the schema already documents that slug or secret_id must be provided as alternatives. The description reinforces lookup by slug or id but does not add format details or selection guidance beyond the schema, so baseline 3 is appropriate.

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?

States a specific verb and resource: get a single secret by slug or id, with the scope explicitly limited to metadata. This clearly distinguishes it from the sibling list_secrets and from mutation tools that would change a 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?

Explicitly says this tool cannot set or change a secret's value and directs the user to the web dashboard for that. The usage context is clear, though it does not explicitly name list_secrets as the alternative for browsing multiple secrets.

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