influx-show-retention-policies

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

With no annotations, the description carries the burden but only states it lists data. It implies a read-only operation but does not explicitly confirm no side effects, auth requirements, or rate limits. For a list tool, this is minimally adequate but lacks explicit safety guarantees.

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?

A single sentence with no redundancy. The verb 'List' is first, followed by the resource and key details. Every word contributes to the purpose.

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 tool with 2 required parameters and no output schema, the description is nearly complete. However, it does not describe the return format (e.g., array of objects) or how to interpret the results. A minor gap given low complexity.

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%, so both parameters are documented in the schema. The description adds no extra meaning beyond the parameter names and types (e.g., does not explain how 'duration' is formatted or the role of 'datasourceId'). Baseline of 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?

The description clearly identifies the tool's action ('List'), resource ('retention policies'), and scope ('for an InfluxDB database'), while noting included details ('duration and replication'). Sibling tools like influx-show-databases or influx-show-measurements handle different entities, so this distinguishes well.

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 guidance on when to use this tool versus alternatives (e.g., other influx-show-* or query-datasource). There is no mention of prerequisites (e.g., valid datasourceId and database) or exclusion criteria.

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