mysql_describe_database

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

No annotations provided, so description must disclose behavior. It does not mention whether the tool is read-only, what happens if the database doesn't exist, or any side effects. Minimal info.

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 (one sentence) but under-specified. It could be longer without becoming verbose; e.g., it should include what 'definition' entails.

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 no output schema, no annotations, and sibling tools, the description is insufficient. It does not explain the return format, error behavior, or when to use this over other inspection tools.

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 coverage is 0%, meaning description should clarify parameter meaning. It only reiterates the parameter name as 'database' without adding context (e.g., expected format or examples). The schema already defines it as a string, so no added value.

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 states 'Inspect a database definition', which is a specific action on a database resource. It vaguely distinguishes from siblings like mysql_list_databases (list names) and mysql_create_database (create), but 'inspect' is ambiguous—could mean show schema options or tables.

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 vs. alternatives like mysql_list_databases or mysql_show_grants. The description lacks context about prerequisites or limitations.

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