create_index

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

The description does not reveal behavioral traits like whether the operation is blocking, its effect on existing indexes, or required permissions. With no annotations provided, the description fails to compensate, leaving the agent uninformed about potential side effects.

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?

The description is extremely concise (five words), but it lacks detail essential for understanding, making it under-specified rather than efficiently concise.

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 the tool has 6 parameters and no output schema, the description is far too minimal. It fails to explain indexing concepts, the uniqueness parameter, or the order of columns, leaving significant gaps for an AI agent.

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?

With only 33% schema description coverage, the description adds no parameter-specific details. It does not explain the meaning of 'columns', 'unique', or 'index_name', relying entirely on the sparse schema, which is insufficient for correct invocation.

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 'Create an index on a table', which is a specific verb+resource combination. It clearly identifies the action (create) and the target (index on a table), distinguishing it from siblings like drop_index and list_indexes.

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 is provided on when to use this tool versus alternatives, such as analyze_query or create_database. There is no mention of prerequisites (e.g., table must exist) or conditions for use.

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