get_mysql_status

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

Description accurately portrays the tool as a read operation but does not explicitly state it is non-destructive or safe. No annotations exist, so the description carries the transparency burden but offers minimal behavioral detail.

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?

Single sentence efficiently conveys purpose and return data. Could be slightly more structured but is adequately concise without verbosity.

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?

Despite no output schema, the description enumerates key fields (version, uptime, connections, query statistics), giving the agent a reasonable understanding of the return format. Simple tool scope makes 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?

Input schema has 100% coverage with a clear description of the optional 'server' parameter. The tool description adds no additional parameter semantics beyond the schema; it only describes the return content.

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?

Description clearly states the verb 'Get', the resource 'MySQL server status', and lists specific data fields (version, uptime, connections, query statistics). This distinguishes it from sibling tools like list_mysql_databases and get_service_status.

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?

Description implies usage for retrieving MySQL status but provides no explicit guidance on when to prefer this tool over siblings like test_server_connection or get_service_status. Lacks exclusions or alternative tool mentions.

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