schema_evaluate_full_tool

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

No annotations provided. The description does not disclose side effects (e.g., mutations, state changes) or behavioral traits like required permissions or resource consumption. It only hints at running EXPLAIN but not whether it modifies anything.

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?

Two sentences, but the second sentence is vague ('Generic: you supply queries...'). Could be more informative without much added length.

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?

With 8 parameters, no parameter descriptions, and no output schema details despite an output schema existing, the description is severely incomplete. It fails to guide the agent on using the tool properly.

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 8 parameters have 0% schema description coverage. The description mentions query_profiles_json and seed_sql_json but does not explain their format, purpose, or defaults. No guidance on how to supply queries or seed SQL.

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 states it loads schema, runs EXPLAIN, and evaluates, which is a specific sequence of actions. However, 'evaluate' is vague and it doesn't clearly differentiate from sibling tools like schema_evaluate_tool or schema_explain_tool.

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. The phrase 'One-shot' implies convenience but lacks explicit context for when it's appropriate or when to prefer other tools.

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