list-flink-statements

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions sorting, filtering, and pagination traits, but lacks critical details: it doesn't specify default sort order, what happens when no filters are applied, whether results are cached, rate limits, authentication requirements, or error conditions. For a list operation with 7 parameters, this leaves significant behavioral gaps.

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, efficient sentence that front-loads the core functionality ('retrieve...list of all statements') followed by key operational characteristics. Every word earns its place with zero redundancy or unnecessary elaboration.

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 list tool with 7 parameters and no output schema, the description is minimally adequate. It covers the basic operation but lacks details about return format, error handling, and behavioral constraints that would be helpful given the parameter complexity. Without annotations or output schema, more context about what the tool returns would improve completeness.

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%, so the schema already documents all 7 parameters thoroughly. The description adds minimal value beyond the schema by implying that parameters enable filtering and pagination, but doesn't provide additional semantic context about parameter interactions or usage patterns. Baseline 3 is appropriate when schema does the heavy lifting.

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 ('retrieve') and resource ('list of all statements') with specific operational characteristics ('sorted, filtered, paginated'). It distinguishes from siblings like 'read-flink-statement' (singular read) and 'create-flink-statement' (creation), but doesn't explicitly differentiate from other list tools like 'list-clusters' or 'list-connectors' beyond the resource type.

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 versus alternatives is provided. The description mentions filtering capabilities but doesn't specify when filtering is appropriate or when other tools (like 'search-topics-by-name' for different resources) should be used instead. Usage context is implied but not articulated.

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