s3_show_key

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

Annotations already declare readOnlyHint=true and openWorldHint=true. The description adds the critical security warning 'СЕКРЕТ: не логировать и не передавать третьим лицам' (SECRET: do not log or pass to third parties) and specifies that the key is 'decrypted', which conveys the sensitive nature of the returned data beyond what annotations provide.

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 a single concise sentence stating the purpose, followed by a terse security directive. No filler or redundant information; every part earns its place and the key purpose is front-loaded.

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 two-parameter tool with an enum and no output schema, the description adequately conveys the operation's outcome (returns the decrypted key) and the mandatory security constraint. Combined with the schema and annotations, no essential information is missing for an agent to call it correctly.

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 description coverage is 100%, with both parameters already documented (key_type enum and account_id description). The description adds no additional parameter-level detail, so the baseline 3 applies; the schema carries the full semantic burden.

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 the verb 'get', the resource 'decrypted S3 access key', and the specific API path (s3/show_key). It unambiguously distinguishes from other S3 tools (e.g., s3_get_users, s3_get_buckets) by naming the exact key retrieval operation.

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?

The description does not explicitly state when to use this tool versus alternatives, nor does it provide exclusions. However, the account_id parameter description hints at consulting s3_get_users for account IDs, which indirectly guides usage context. This is minimal but not entirely absent.

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