create_sheet

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

With no annotations, the description carries the behavioral burden and discloses specific effects: margins zeroed, plot rotation cleared, auto-viewport removed, and returns measured sheet size. However, it does not fully clarify the destructive implications of 'reset' on existing user-defined content.

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, dense sentence with a colon-delimited list of effects. It packs a lot of specific information efficiently without unnecessary verbosity.

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 an output schema and three parameters, and the description covers return value and key behavioral details. It lacks context on prerequisites or how the name and landscape parameters affect the result, but overall the core behavior is well covered.

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 schema has 0% description coverage, and the description only implies the size parameter accepts A4..A0. It does not explain the landscape or name parameters, leaving meaningful gaps in parameter understanding.

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 creates or resets a paper-space sheet (layout) with sizes A4..A0, specifying it is for 1:1 plotting. It distinguishes itself from sibling tools like add_viewport or title_block by focusing on the sheet-level setup.

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 implies usage for preparing a clean layout for plotting, but it does not explicitly state when to prefer this over alternatives such as add_viewport or title_block. No exclusions or conditions are provided.

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