plasticity_download_and_import_reference_mesh

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

Annotations only flag destructive/openWorld/readOnly=false; the description goes well beyond by disclosing concrete safeguards (pins a public IPv4, limits redirects, caps payloads at 64 MiB, validates mesh structure and finite coordinates, stores a private SHA-256-addressed artifact) and side effects (journaled import with redacted provenance and measured bounds). This is exactly the extra behavioral context the annotations cannot convey.

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?

Front-loaded with the action and target, then proceeds through unit rationale, safeguards, journaling, and the fit-critical caveat. Every sentence carries information, though the run of security/safeguard clauses is dense and slightly list-like rather than tightly prioritized.

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?

For a mutating, open-world tool with 5 parameters, a nested source object, and no output schema, the description supplies a strong behavioral and caveat layer that an agent needs before invoking correctly. It is slightly incomplete only in leaving several enum/nested parameters and the response/journal lookup path unaddressed.

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 carries the burden, and it explains the trickiest parameter well (why sourceUnit is required for unitless STL and ambiguous community scale) and clarifies format and the public-HTTPS source URL. But it leaves revision, intent, confidence, sourceKind, license, and sourcePageUrl unexplained, so the nested source object and several enum fields remain undocumented.

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?

States a precise compound verb ('download and import') plus the exact resource (one explicitly selected HTTPS STL or OBJ file) and its end state (approximate reference mesh in Plasticity). It clearly differentiates itself from the download_and_import_reference_3mf / _step / _parasolid siblings and from local plasticity_import_reference_mesh by naming the specific formats and network path.

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?

Gives clear context: one explicitly selected public-hostname file, must declare sourceUnit, and an explicit when-not ('do not use it as a fit-critical datum without checking official drawings or user-confirmed measurements'). It does not, however, name the alternative sibling to use for 3MF/STEP/Parasolid or for local files, so routing between it and those import tools is left to inference.

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