Create a record

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

Discloses critical behaviors beyond annotations: dry-run default, the need for confirm=true, and the ALLOW_WRITES deployment flag. This adds substantial context that annotations (readOnlyHint false, destructiveHint true) do not fully cover.

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, no fluff, front-loaded with purpose then key behavioral caveats. Every sentence earns its place.

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?

Covers the essential invocation behavior (dry-run, confirm, ALLOW_WRITES) and gives a hint about return ('preview of exact payload'). It lacks details on error responses or execute-mode return, but is sufficient for a simple create tool with no output schema.

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 covers 100% of parameters with descriptions, but the description adds the crucial ALLOW_WRITES dependency and reinforces confirm flag semantics, going slightly beyond 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 'Create a new record in the upstream system', using a specific verb and resource. It distinguishes from the sibling 'list_records' by its create action and mentions the upstream system.

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?

Provides clear usage context: creation requires confirm=true to execute, defaults to dry-run, and requires ALLOW_WRITES enabled. However, it does not explicitly mention using the sibling tool for reading, so it's not a full 5.

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