generate_tot

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

With no annotations, the description carries the burden of behavioral disclosure. It explains that it inserts a field block and collects specific captions, but does not mention whether it updates existing fields, handles missing paragraphs, or any side effects. Some context is provided, but gaps remain.

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 brief: two sentences with clear subject-verb-object structure. The first sentence states the primary action, the second adds detail on content. However, it could be more compact by combining or removing redundancy.

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?

Despite having an output schema (which explains return values), the description lacks usage guidelines and fails to fully explain parameter semantics. For a tool that modifies document structure, more context on behavior and constraints is needed for safe invocation.

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%, so the description must compensate. The description clarifies that `para_id` is the paragraph after which to insert, but does not explain `title`'s purpose (only its default is shown). This partial coverage leaves the agent uncertain about the second parameter's role.

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 clearly states the tool inserts a Table of Tables field block after a specific paragraph, and explains what it collects (caption-styled paragraphs starting with 'Table'). This is a specific verb+resource, distinguishing from sibling tools like generate_list_of_tables which likely generate a list rather than a field block.

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 provides no guidance on when to use this tool versus alternatives like generate_toc or generate_list_of_tables. It does not specify prerequisites (e.g., existing captions, paragraph existence) or when not to use it.

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