dune-mcp

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

With no annotations provided, the description carries full burden for behavioral disclosure. While it mentions the table must exist and shows an example, it doesn't address critical aspects like required permissions, whether the operation is idempotent, error handling for duplicate rows, or performance characteristics like batch size limits.

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 well-structured and front-loaded with the core purpose, followed by clearly labeled sections for Args, Returns, and Example. Every sentence adds value with no redundancy, making it easy to scan and understand quickly.

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 mutation tool with 3 parameters, 0% schema coverage, and no annotations, the description provides basic operational context but lacks important details about permissions, constraints, and error scenarios. The presence of an output schema helps with return values, but behavioral aspects remain underspecified.

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%, but the description provides meaningful context for all 3 parameters: it explains namespace and table_name identify the target, and rows must match column names. The example further clarifies row structure. This compensates somewhat but doesn't fully document data types, constraints, or validation rules.

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 ('Insert rows') and target resource ('into an existing table'), making the purpose immediately understandable. However, it doesn't explicitly differentiate this from sibling tools like 'upload_csv' or 'create_table', which might handle similar data insertion scenarios.

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 'upload_csv' or 'execute_sql'. It mentions the table must be 'existing' but doesn't clarify prerequisites, error conditions, or typical use cases compared to sibling tools.

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