get_named_query

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only says 'Get details'. It does not state whether the call can fail on unknown IDs, what subset of fields is returned, whether any special permissions are required, or any other runtime behavior beyond the read-only implication.

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 short and front-loaded, with no unnecessary fluff. The Args section is somewhat redundant with the schema, but it does not detract significantly from readability.

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 get-by-id tool, the description is minimally functional but incomplete. The presence of an output schema reduces the need to explain return fields, yet the lack of usage guidance, error behavior, and relationship to sibling tools like list_named_queries makes the context incomplete for an agent choosing among many Athena-related tools.

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?

The description includes an Args section clarifying that named_query_id is the named query ID, which is minimally helpful. However, schema description coverage is 0%, and the description simply repeats what the schema title already conveys rather than adding context such as where the ID comes from or its format.

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 ('Get') and resource ('named query'), making the core action clear. However, it does not explicitly contrast with the sibling list_named_queries or indicate that this retrieves a single item by ID, so sibling differentiation is weak.

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 provided about when to use this tool instead of list_named_queries, get_query_execution, or other related siblings. There is no mention of typical workflows or how an agent should obtain a valid named_query_id.

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