db_describe_schema

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

Annotations are absent, so the description bears the full burden of disclosure. It mentions the introspective action but does not state whether it is read-only, what the return structure looks like, or any potential side effects or limitations. The parenthetical only hints at scope without clarifying behavior.

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 brief and front-loaded with the primary action, followed by a compact argument list. For a tool with a single parameter, this is appropriately sized with no wasted words, though it could include a bit more context without becoming verbose.

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?

Given that an output schema exists, the description does not need to elaborate on return values. It states the purpose clearly enough for a simple introspection tool, but lacks any usage context, such as which connection types are supported or when to prefer this over sibling tools. It is minimally adequate but leaves gaps.

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%, yet the description's explanation of connection_id as 'The DB Console connection id' adds little beyond the parameter name itself. It does not provide format, source, or validation context, failing to compensate for the missing schema documentation.

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 'introspect' and the resource 'connection', with a parenthetical listing the levels (databases / schemas / tables / columns). This makes the core purpose unambiguous and distinguishable from Athena-specific siblings by the explicit mention of 'DB Console connection', though it does not name any specific sibling.

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?

There is no guidance on when to use this tool versus alternatives like db_query, athena_list_tables, or athena_describe_table. No prerequisites, exclusions, or contextual cues are provided, leaving the agent to infer usage from the name alone.

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