list-connections

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

With no annotations, the description takes on the burden of disclosing behavior. It explicitly states that sensitive fields (password, extra) are redacted and describes the return type, which are meaningful behavioral traits. However, it does not explicitly declare read-only status or side effects, but 'list' strongly implies non-mutating 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 main sentence is concise and front-loaded. The Args and Returns sections are structured, but they largely duplicate schema information, adding some redundancy. Overall length is appropriate for a tool with 5 parameters.

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 operation, the description covers the essential behavior: listing connections, redaction, and return type. With no output schema, it does not detail the structure of connection objects beyond redaction, but the schema covers parameter semantics. The lack of error handling or auto-selection behavior is partially mitigated by the schema, making this sufficient.

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?

All 5 parameters are thoroughly described in the input schema (100% coverage), covering purpose, defaults, and optionality. The tool description merely repeats these in the Args section without adding new meaning. The only additional element is 'ctx', which is a standard MCP context and not a user-facing parameter.

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 'List Airflow connections in an MWAA environment', specifying the verb (list), resource (connections), and context (MWAA environment). This distinguishes it from siblings like list-dags or list-environments, and the mention of redaction adds specificity.

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?

It implies usage for retrieving connections with clear context (MWAA environment) and mentions redaction, but does not explicitly reference alternatives or when-not-to-use. For a straightforward read operation, the context is sufficient.

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