sch_create_page

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It only states the tool creates a page but offers no details on side effects (e.g., whether it modifies the schematic immediately), required permissions, or what constitutes a 'page' in this context. The mutation nature is implied but not explicitly stated.

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, concise sentence that directly conveys the tool's purpose. It contains no extraneous words and is efficiently front-loaded.

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 tool's simplicity (one parameter, no output schema, no annotations), the description is too brief. It lacks information on success/error responses, what a 'page' entails, and any constraints (e.g., maximum pages). The agent may not have enough context to invoke the tool confidently or handle outcomes.

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 input schema has one parameter, schematicUuid, with 0% coverage in the description. The description adds minimal context by mentioning 'under an existing schematic', hinting at the parameter's role. However, it does not clarify the format of the UUID, how to obtain it, or that it's a required parent reference, leaving semantic gaps.

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 ('Create') and the object ('a new page under an existing schematic'). This distinguishes it from sibling tools like sch_create_schematic (creates a new schematic) and sch_create_wire (creates a wire), as it specifically targets page creation within an existing schematic.

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, exclusions, or required conditions. For example, it doesn't state that the schematic must already exist or that additional parameters like page name might be needed. The agent is left without context to decide the appropriate tool.

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