athena_list_saved

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

With no annotations available, the description carries the full burden of behavioral disclosure. It clearly states a read-only list operation scoped to the caller and mentions optional workspace filtering, both of which are meaningful behavioral traits. It does not detail ordering or pagination, but the output schema covers return expectations.

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 two sentences plus a minimal Args block, with the main statement front-loaded. Every element earns its place, and the parameter explanation is concise without redundancy.

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 one optional parameter and an output schema, the description is nearly complete. It could note a dependency on athena_list_workspaces for valid workspace ids, but that is a minor omission given the straightforward nature of the tool.

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 0%, so the description must compensate for the sole parameter. The Args section fully explains workspace_id as an optional Athena workspace id used to filter the list, adding semantic meaning beyond the bare schema type definition.

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 uses a specific verb ('List') and a clearly defined resource ('the caller's saved Athena queries'), which immediately distinguishes it from siblings like athena_run_query, athena_history, and db_list_saved. The scope ('caller's') and resource type ('saved') make the purpose unambiguous.

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 implies when to use the tool (when listing saved Athena queries) but does not explicitly name alternatives or exclusion conditions. An agent can infer differentiation from sibling names, but the text itself provides no direct guidance such as 'use athena_history for past executions'.

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