List Redshift AOVs

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

No annotations are provided, so the description carries the full behavioral disclosure burden. The 'active or named RenderData' clause usefully reveals the fallback/default targeting semantics, and 'List' implies a read-only operation. However, it does not disclose failure behavior (missing active RenderData, unknown name), return format, or whether an empty list versus an error is returned.

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 front-loaded sentence that wastes no words: verb first, resource second, scope last. Every element earns its place and the sentence is immediately scannable.

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 tool with only two optional parameters and a complete schema, the description is mostly adequate, covering the core scope. However, with no output schema and no annotations, it leaves two meaningful gaps: what the invocation returns (a flat list of names versus structured objects) and error behavior when no RenderData is active or the named one does not exist.

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%, giving a baseline of 3, but the description adds genuine semantic value by clarifying that omitting render_data_name targets the active RenderData. The schema merely labels the parameter as 'RenderData name,' while the description conveys the defaulting behavior that actually determines how the optional parameter should be used.

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 states a specific verb ('List'), a precise resource ('Redshift AOVs'), and a scope ('from the active or named RenderData'), which clearly separates it from mutation siblings like rs_upsert_aov, rs_remove_aov, and rs_clear_aovs. It is clear and accurate, though it does not explicitly name a sibling it is not, so it stops short of a 5.

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 is given on when to use this tool versus alternatives. The phrase 'active or named RenderData' implies a targeting behavior, but there is no explicit when/when-not guidance, no prerequisites (e.g., must a document or RenderData exist first?), and no mention of related AOV mutation tools.

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