mysql_setup_persistent

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It mentions 'persistent connection' and 'default credentials' but doesn't explain what persistence entails (e.g., connection pooling, reuse), authentication requirements beyond parameters, or potential side effects like resource consumption.

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?

Extremely concise with a single, clear sentence that front-loads the core purpose. No wasted words or redundant information.

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 connection setup tool with 7 parameters, no annotations, and no output schema, the description is insufficient. It lacks details on what 'persistent' means operationally, what 'default credentials' implies, error handling, or what successful setup returns, leaving significant gaps for agent understanding.

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 fully documents all 7 parameters. The description adds no additional parameter semantics beyond what's in the schema, maintaining the baseline score of 3 for high coverage.

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 action ('Set up') and resource ('persistent connection'), specifying it uses 'default credentials'. It distinguishes from 'mysql_connect' by implying persistence, but doesn't explicitly differentiate from all siblings like 'mysql_status' or 'mysql_disconnect'.

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 on when to use this tool versus alternatives like 'mysql_connect' or other siblings. The description mentions 'default credentials' but doesn't explain what that means or when this is preferred over other connection methods.

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