table_load

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

With no annotations, the description discloses merge/replace behavior but omits details on side effects, error handling, or permissions. Adequate but could be more transparent.

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?

Two sentences, efficient and to the point. No unnecessary words, but it comes at the cost of completeness.

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?

No output schema, no annotations, and minimal description. Lacks details on return values, errors, or file format specifics. Incomplete for a file-loading tool.

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 description must compensate. It explains merge's effect ('keeps existing entries; otherwise replaces') but does not elaborate on path. Adds meaningful value over 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 clearly states 'Load a .CT file' with a specific verb and resource, and the merge option distinguishes it from siblings like table_add or table_clear.

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?

It explains the merge vs replace behavior, guiding usage. However, it lacks explicit when-to-use or alternatives, but the context of sibling tools is enough.

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