index_health

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

No annotations provided, so description carries full burden. It implies a read-only operation but does not state it explicitly or mention performance impact, permissions, or how 'flag' manifests (e.g., return column). Adds some value beyond schema but insufficient for full transparency.

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, no wasted words. However, could be restructured to front-load key behaviors or output hints while maintaining conciseness.

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?

Lacks output description; no output schema exists, so description should explain what columns are returned (e.g., index name, cardinality, duplicate flag). Also does not address the 'table' parameter gap for a tool that clearly needs a table to list indexes on.

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?

Only 2 of 3 parameters have schema descriptions; the tool description does not elaborate on parameter meaning. The 'table' parameter lacks description in both schema and description. Parameter semantics are poorly covered.

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 verb 'List' and resource 'indexes with cardinality and flag possible duplicates'. Distinguishes from sibling 'list_indexes' which likely only lists names, by adding cardinality and duplicate detection.

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 over alternatives like list_indexes or other diagnostic tools. No prerequisites or context provided.

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