scene_export

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

Description claims 'Export' and 'saves' (write operations) but annotations set readOnlyHint=true, contradicting the actual behavior. No details on error handling or side effects beyond prerequisite.

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, front-loaded with purpose, no redundant words. Every sentence adds essential information: action, prerequisite, output location.

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?

No output schema, but description covers what the tool does, what it requires, and where output is saved. Lacks details on success/error feedback, but adequate for the tool's simplicity.

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 covers all parameters with descriptions. Description adds value by clarifying that omitting 'name' exports the entire scene, and 'binary' defaults to true. Provides usage context beyond schema.

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?

Explicitly states 'Export scene or specific object as GLB', clearly identifying the action (export), resource (scene/object), and format (GLB). Distinguishes from sibling 'take_screenshot' which is image-based.

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?

Mentions prerequisite 'Requires GLTFExporter in your app' and output location 'Saves to screenshots/ folder'. Lacks explicit when-to-use or when-not-to-use compared to siblings, but context is clear.

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