Contract Testing: Get Secret

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

Annotations already provide readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds 'Retrieve metadata', which aligns but does not disclose additional behavior beyond what annotations cover (e.g., no mention of auth requirements or response format).

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 extremely concise (one sentence plus a parameter list), front-loads the purpose, and contains no superfluous content. Every sentence serves a clear role.

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?

Given the lack of an output schema, the description does not elaborate on what 'metadata' includes (e.g., name, creation date, value reference). This leaves ambiguity about the return value, making it less complete than it could be for a simple retrieval 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?

Input schema has 100% coverage, with the description repeating 'UUID of the secret' for secretId. No additional meaning or context beyond the schema is provided, so this meets the baseline without adding value.

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 clearly states 'Retrieve metadata for a specific secret by UUID', with a specific verb and resource, and it is well-differentiated from sibling tools like create_secret, delete_secret, update_secret, and list_secrets.

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?

No explicit guidance on when to use this tool vs alternatives. While the context implies it is for fetching a single secret by UUID, the description does not clarify scenarios or mention exclusions, such as when list_secrets might be more appropriate.

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