mark_sharp_edges

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

Describes visual effect (hard crease vs smooth blend) but does not disclose whether operation is additive or overwrites existing sharpness, or any side effects on modifiers. With no annotations, description carries full burden, adequate but not thorough.

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?

Concise one-paragraph structure with clear separation of purpose and parameter descriptions. No unnecessary words, every sentence adds value.

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?

Covers purpose, parameter details, and visual output. Missing notes on prerequisites (auto-smooth enabled, Edge Split modifier) and reversibility. Given complexity, adequate but not exhaustive.

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?

Adds significant value beyond schema: explains edge_indices format ('comma-separated or all') and sharp parameter meaning (true=hard, false=soft). Schema coverage was 0%, so description compensates fully.

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's function: marking edges as sharp or soft, and explicitly links it to auto-smooth and Edge Split modifier. It distinguishes from siblings like set_edge_crease by focusing on smooth shading behavior.

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?

Provides clear context: sharp edges create creases under smooth shading, soft edges blend. Implicitly tells when to use, but does not explicitly mention when not to use or alternatives.

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