pad_append

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

With no annotations provided, the description bears the burden of behavioral disclosure. It communicates that the operation is non-destructive (append to end) and mentions a concurrency guard, which is valuable. However, it does not state what happens on revision mismatch, whether the pad must already exist, or what side effects occur beyond appending.

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 two short sentences with no filler. The primary action is front-loaded, and the expected_revision note earns its place by adding an important usage detail. This is appropriately sized for the tool's complexity.

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 simple append operation with an output schema, the description covers the core behavior and a key optional parameter. It misses important context like failure behavior on concurrent writes, whether a missing pad is created, and any permission requirements, which would be especially relevant since annotations are absent.

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?

Input schema coverage is low at 25%, but the description adds meaning for expected_revision by explaining its concurrency-guard purpose CST. project_id already has a detailed schema description, while pad_id and content are self-evident from their names and types. The description provides partial compensation but does not document every parameter's intended behavior.

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 ('Append content') and the resource ('to the end of a pad'), which unambiguously distinguishes it from sibling tools like pad_write or pad_edit. The specific append-only semantics make the tool's purpose immediately obvious.

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 core usage context is explicit: append to a pad when adding content to its end. The optional expected_revision parameter is given a clear purpose ('guards against concurrent writes'), telling the agent when to use it. It does not explicitly name alternatives or exclusions, but the append operation is distinct enough to serve as clear usage guidance.

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