lathe_shape

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

Discloses a key behavioral trait: 'The browser window auto-refreshes so the user sees the change immediately.' However, with no annotations provided, the description carries the full burden and omits other side effects like persistence or error behavior, limiting transparency to moderate depth.

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: the first states the main purpose, the second covers behavior and usage. Every sentence earns its place with no redundancy or filler.

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 its simplicity (two parameters, no output schema), the description adequately covers purpose, usage, and a key behavior. It could mention error handling or return behavior, but such details are not essential for a basic push/update tool.

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 100% for both parameters, so the description adds limited additional meaning. It mentions 'optionally a different template,' which aligns with the template parameter but doesn't go beyond the schema's own descriptions.

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: 'Push updated resume data (and optionally a different template) into the live preview.' The verb 'push' plus the specific resource 'live preview' distinguishes it from sibling tools like lathe_templates or lathe_preview.

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?

Explicitly instructs 'Use this after every feedback iteration,' which tells the agent when to invoke the tool. It doesn't mention when not to use it or describe alternatives, but the given guidance is direct and actionable.

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