Retrieve Key Value connection info

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

Annotations already declare readOnlyHint and idempotentHint. Description adds that connection info includes sensitive information, which is important for authorization awareness, and specifies the exact API call, providing context beyond annotations.

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?

Description is concise but has slight redundancy: first sentence repeats title. The API endpoint line adds value. Could be improved by removing the first sentence.

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?

No output schema; description does not specify what the connection info contains beyond 'sensitive information'. Missing details on error states, auth requirements, or response structure, leaving gaps for an AI 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?

Only parameter redisId has no description in input schema (0% coverage). Description merely says 'by ID' which is minimal. No explanation of format, validation, or source for the ID.

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 'Retrieve' and resource 'Key Value connection info' by ID. Differentiates from sibling retrieval tools like render_retrieve_key_value and render_retrieve_redis_connection_info by specifying 'connection info', but does not explicitly distinguish them.

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: retrieve connection info for a Key Value instance. No explicit guidance on when not to use or alternatives, but the purpose is straightforward.

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