export_gltf

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

No annotations are provided, so the description carries full burden. It mentions action_names but does not disclose behavioral traits such as whether the operation is destructive, if it overwrites files, or if it requires specific permissions. This is insufficient for a tool with four parameters and no annotation support.

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 extremely concise, consisting of two short sentences with no extraneous words. It front-loads the purpose and adds one key parameter detail efficiently.

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?

Despite the presence of an output schema, the description omits critical context: what the tool returns, how the export works (saves to file?), and any side effects. Given four parameters and no annotations, the description is incomplete for an AI agent to use reliably.

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 description coverage is 0%, so the description must explain parameters. It only addresses action_names, leaving output_path, export_format, and apply_transform undocumented. The schema titles provide minimal information; this does not compensate for the lack of description.

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 'Export glTF/GLB', which is a specific verb and resource. It also hints at the action_names parameter, but does not clarify the context (e.g., exports current scene) or distinguish it from sibling export_to_summit. Thus, it's clear but lacks sibling differentiation.

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 guidance on when to use this tool versus alternatives like export_to_summit. The description does not provide any context on prerequisites, when it is appropriate, or when to choose another tool.

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