add_table

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

No annotations are provided, so the description must disclose all behavioral traits. It mentions 'tracked insertion' but does not explain whether tracking is automatically enabled, what happens to the paragraph after insertion, or any side effects. For a mutation tool, this is insufficient.

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 a single sentence, concise with no wasted words. However, it could be structured with additional details like parameter explanations without being overly verbose.

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 output schema exists but is not referenced, and no return value is mentioned, the description is incomplete. The 5 parameters are mostly unexplained. Sibling tools indicate many table operations, so more context about when to use this tool is needed.

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 description coverage is 0%, yet the description does not explain any parameter meaning. Required parameters like 'para_id' are not described as the target paragraph ID. 'rows' and 'cols' are self-explanatory but still undocumented. 'author' and 'document_handle' are completely unaddressed. The description fails to compensate for the lack of schema documentation.

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 action: inserting a new table after a paragraph with tracked insertion. It uses a specific verb ('Insert') and resource ('table'), and distinguishes from sibling tools that modify existing tables (e.g., add_table_row, add_column_to_table).

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. No prerequisites (e.g., document must be open, paragraph must exist) or exclusions are provided. The description lacks context for decision-making.

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