apply

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

With no annotations, the description must carry the full load for behavioral transparency. It only states the action without disclosing side effects, destructive nature, idempotency behavior, permissions, or what happens to existing data. The mention of 'dress' implies modification but lacks necessary detail.

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 a single, front-loaded sentence of 13 words that efficiently conveys the core action and scope. Every word earns its place, with no fluff or repetition.

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 tool has no output schema and no annotations, yet the description omits operational details such as return values, error conditions, or the effect of the idempotency key. The agent lacks sufficient context to understand the full lifecycle of using this tool, making it incomplete for a complex operation.

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?

The description adds meaning beyond the schema by explaining that the template applies overlays and beat grid to the sheet. This contextualizes the 'template' and 'sheet' parameters beyond their raw definitions, despite the schema already having 100% coverage.

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 applies a named template to a cut sheet, specifying that it affects overlays and beat grid. The verb 'dress' is domain-specific but still conveys the intended action on a specific resource, distinguishing it from sibling tools like 'draft' or 'splice'.

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 no guidance on when to use this tool versus alternatives, nor does it mention prerequisites, contraindications, or typical workflows. Without any usage context, an agent has no basis to decide between 'apply' and other sibling tools.

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