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

Annotations indicate read-only is false (write operation), destructive is false, and idempotent is false. The description adds context that it generates a GLB file and requires prior image upload, but it does not disclose any side effects, such as cost, rate limits, or whether it overwrites existing creations. Given that annotations are minimal and do not cover behavior beyond safety, the description provides some value but not rich detail.

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 only three sentences. It front-loads the core purpose ('Image-to-3D GLB'), then provides key usage steps and model options. Every sentence adds value: prerequisite, animation link, and model defaults. No fluff or redundant content.

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's moderate complexity (6 parameters, no output schema), the description is fairly complete for a basic generation tool: it covers purpose, prerequisite, model selection, and a follow-up. However, it omits information about output (since no output schema) and does not define the effect of parameters like faceLimit or textureQuality, which could affect generation choices. This is a reasonable minimum viable description.

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 6 parameters, but the description only mentions the 'model' parameter (listing options) and implicitly references 'creationIdentifier' through the upload prerequisite. Schema description coverage is 0%, meaning the description adds little semantic value for parameters like 'faceLimit', 'resolution', 'textureQuality', and 'folderReference'. Since the schema itself provides types and enums, the description only partially compensates, warranting a baseline score of 3.

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: 'Image-to-3D GLB', which indicates the verb (generate) and resource (3D GLB from an image). It also mentions an animation tool ('models3d_rig') and lists available models, distinguishing it from other generation tools in the sibling set (e.g., magnific_images_generate). However, it does not explicitly contrast with sibling tools, only hints at the workflow.

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 usage by stating 'Upload external images first' and 'Animate with `models3d_rig`', providing clear prerequisite and follow-up actions. However, it does not explicitly state when to use this tool over alternatives, nor does it mention any exclusions, which would be helpful given the large number of sibling generation tools.

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