mesh.shade_smooth

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

Without annotations, the description carries the burden of behavioral disclosure. It correctly states the effect (smooth/flat shading toggle), but does not mention whether the change is reversible, if it affects the entire mesh or selected faces, or any side effects (e.g., requires edit mode). It is correct but minimal.

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 conveys the core action. It is front-loaded with the verb and resource. However, it could be slightly more informative without becoming verbose.

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 absence of an output schema and low parameter coverage, the description should provide more context. It does not explain return values, default behavior, or how the tool interacts with the 3D viewport. A more complete description would mention that it sets the shading of the entire mesh object and that the default object is the active selection.

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, meaning no additional text beyond titles. The description does not elaborate on the parameters (e.g., what 'object' expects or how 'smooth' interacts with defaults). Baseline for low coverage is 4, but description fails to compensate.

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 ('Toggle smooth/flat shading') and the target ('on the object'). It specifies the resource and verb, and the tool name 'mesh.shade_smooth' further disambiguates it from material shading tools. However, it does not explicitly state that it operates on mesh objects, which might be inferred from the prefix.

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?

No usage guidance is provided. The description does not indicate when to use this tool versus alternatives like shading tools or other mesh modifiers. There is no mention of prerequisites, context, or when not to use it.

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