generate_list_of_tables

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

No annotations provided; the description only states action and prerequisite, lacking disclosure of side effects (e.g., cursor position, overwrite behavior) or output details.

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 of 11 words, front-loaded with action, no wasted words. Perfectly 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?

For a simple insert tool with no parameters and existing output schema, the description covers purpose and prerequisite but lacks mention of insertion location or output behavior.

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?

No parameters exist, so baseline is 4. The description adds value by stating the prerequisite condition, which goes beyond the empty schema.

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 specifies the verb 'Insert' and resource 'List of Tables field', with a clear prerequisite 'requires SEQ Table captions', which distinguishes it from siblings like generate_list_of_figures.

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?

The description implies use when SEQ Table captions exist, but does not explicitly state when not to use or name alternatives. However, the prerequisite and sibling list provide context.

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