subdivide

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

With no annotations provided, the description carries the burden of behavioral disclosure. It indicates the operation is applied to all faces and defines parameters, but does not mention whether the operation is destructive, modifies the mesh in-place, or requires any specific object state (e.g., edit mode).

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 concise sentences with front-loaded action and parameter explanations. No wasted words.

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?

For a simple mesh operation with no output schema, the description covers the core functionality and parameters. Minor gaps: does not specify whether the operation is applied to the active object or the named object, or the return value.

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 coverage is 0%, so the description must add meaning. It explains 'cuts' and 'smooth' parameters, but does not explain the required 'name' parameter (likely the mesh object) or constraints (e.g., cuts >= 0). Partial value added.

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 ('subdivide all faces of a mesh') and defines key parameters ('Cuts = number of subdivision levels', 'Smooth > 0 applies smoothing'). It distinguishes itself from siblings like 'decimate' or 'remesh' which perform different mesh operations.

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 increasing mesh resolution but does not explicitly state when to use this tool versus alternatives (e.g., modifiers like 'subdivision_surface'). No when-not-to-use or prerequisite information is provided.

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