pad_write

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

With no annotations, the description must disclose behavior itself. It clearly states the destructive nature of overwrite and the revision mechanism, but does not explain what happens on revision mismatch or pad-not-found errors. It also doesn't mention any permissions or side effects beyond overwrite. This is adequate but leaves important behavioral gaps.

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 with no filler. The primary action and overwrite mechanism are front-loaded, and the alternative guidance is concise. 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?

Given the presence of an output schema (which presumably covers return values) and the schema descriptions for project_id, the description covers the core behavior, overwrite mechanics, and routing to siblings. It could be more complete by addressing error conditions (revision mismatch) but is largely sufficient for an agent to call it correctly.

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 only 33%, so the description should compensate. It explains pad_id and expected_revision for overwrite, and notes name uniqueness per project. However, it does not explain tags or content semantics, though content is self-evident. The description adds some value beyond the schema but doesn't fully cover all 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 states a clear verb-resource pair: 'Create a pad, or fully overwrite one', and differentiates from siblings by explicitly naming pad_append/pad_edit as alternatives for targeted changes. It also notes the uniqueness constraint per project, adding specificity.

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 explicitly instructs to 'Prefer pad_append/pad_edit for targeted changes', providing clear guidance on when this tool is not the best choice. It implies usage for creation or full overwrite, though it doesn't list explicit exclusions beyond that preference.

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