mdb_explain

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

No annotations are provided, so the description carries the full burden. It usefully discloses 'Always rolled back', telling the agent the statement has no lasting effect, but omits whether the query is actually executed for planning only, what the response contains, or any permission requirements. Modest but real added value.

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?

Three short sentences, front-loaded with the action and then the parameter condition. Every sentence carries information; only the quoting of config_label duplicates the schema.

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 two-parameter tool with no output schema and no annotations, the description is roughly adequate, but it leaves the agent unsure of what a rolled-back EXPLAIN returns and whether it is a safe read-only operation. A sentence on the plan/return nature would close the gap.

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 both 'query' and 'database' including the same config-label and dynamic-session conditions. The description largely restates what the schema provides, adding no syntax or format detail beyond it.

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?

States a specific verb and resource ('Run EXPLAIN on a query'), which clearly distinguishes it from the sibling mdb_query that would actually execute a query. It does not explicitly contrast itself with siblings, but the purpose is 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?

Gives conditional guidance on the database parameter ('Omit database if dynamic session active'), which implies this tool is normally used outside an active runtime session. However it never states when to choose EXPLAIN over mdb_query or any prerequisite workflow, so usage is only partially implied.

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