ArcadeDB Multi-Model DBMS

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively communicates that this is a write/mutation tool ('non-idempotent command'), specifies the types of operations (INSERT, UPDATE, DELETE, CREATE TYPE), and provides language preference guidance. However, it doesn't mention permissions requirements, error handling, or transaction behavior.

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 extremely concise and well-structured with only two sentences. The first sentence establishes the core purpose and scope, while the second provides important usage guidance. Every word earns its place with no redundancy or fluff.

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 write/mutation tool with no annotations and no output schema, the description does a good job covering the essential context: purpose, usage guidelines, and behavioral characteristics. However, it could be more complete by mentioning what the tool returns (e.g., affected rows count, success/failure indicators) or any important constraints beyond language preference.

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 100%, so the schema already documents all parameters thoroughly. The description adds some value by explaining the language preference ('Prefer OpenCypher unless SQL is explicitly requested') which provides context beyond the schema's language parameter description, but doesn't add significant semantic details about individual parameters.

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's purpose with a specific verb ('execute') and resource ('non-idempotent command against an ArcadeDB database'), and distinguishes it from siblings by specifying it's for write operations like INSERT, UPDATE, DELETE, CREATE TYPE. It explicitly differentiates from the 'query' sibling tool which likely handles read operations.

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 explicit guidance on when to use this tool ('for INSERT, UPDATE, DELETE, CREATE TYPE, and other write operations') and when to prefer alternatives ('Prefer OpenCypher unless SQL is explicitly requested'). It also implicitly distinguishes from the 'query' sibling tool by specifying write operations.

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