execute_command

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

No annotations are provided, so the description carries full burden. It discloses that commands are non-idempotent and lists write operations, signaling side effects. However, it does not detail error handling, transaction behavior, or authorization requirements, which would enhance transparency.

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: first defines purpose and side-effect, second gives usage guidance. No redundant or extraneous information. Every sentence adds value.

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?

The description covers purpose, usage, and parameter guidance adequately. However, without an output schema, it omits information about return values or error handling. For a write operation, explaining what the command returns (e.g., success indicator or affected records) would improve completeness.

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 100%, so baseline is 3. The description adds value by recommending the default language ('cypher') and when to use SQL, providing guidance beyond the schema. Other parameters are adequately described in the 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 the tool executes non-idempotent commands against an ArcadeDB database and lists write operations like INSERT, UPDATE, DELETE, CREATE TYPE. It distinguishes from sibling tools such as 'query' by specifying that this tool is for write 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?

Explicitly states when to use: for INSERT, UPDATE, DELETE, CREATE TYPE, and other write operations. Also provides guidance to prefer OpenCypher (cypher) unless SQL is explicitly requested, helping the agent select the appropriate language.

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