blender_export_presets

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

With no annotations provided, the description bears full responsibility for behavioral disclosure. It mentions handling scale, format, and bone limits but does not explain side effects (e.g., file creation, scene modification, destructive actions) or behavior for validation and preset creation operations. This is insufficient for a multi-operation tool.

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 concise, with a front-loaded purpose statement and a brief second paragraph. It is efficiently written, though it could be improved by explicitly listing the supported operations to enhance scanability.

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 has 13 parameters and an output schema, the description only covers the export aspect, ignoring validation and preset creation operations. While the output schema covers return values, the description fails to convey the full scope of the tool's capabilities, making it incomplete for the multi-operation nature.

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 100%, so the baseline is 3. The description adds minimal value beyond the schema by mentioning scale, format, and bone limits, but does not elaborate on parameter interactions or defaults. It falls short of compensating for the missing behavioral context.

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 purpose: platform-specific export presets for VR avatar deployment. It highlights handling critical differences between VR platforms and naming specific environments (VRChat, Resonite, Unity), which effectively distinguishes it from generic export tools like 'blender_export'.

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 use for VR avatar export with platform-specific needs but lacks explicit guidance on when to choose this tool over siblings like 'blender_export' or 'blender_validation'. No alternative tools or preconditions are mentioned, leaving the agent to infer usage context.

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