model_export

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

With no annotations, the description carries the full behavioral burden. "Export" implies a read-only operation and "standalone inline-SVG HTML" hints at the serialization approach, but it never says whether the tool returns the exported content directly, a file path, or a download reference, nor whether anything is written or mutated server-side.

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?

One well-formed sentence with zero filler, front-loading the action and the output choices. Brevity is appropriate, though the space saved could have been spent clarifying the return value or the model parameter.

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 annotations and no output schema exist, so the description is the only source of behavioral information, and it omits both the shape of the returned value and the meaning of the required model input. For an export/serialization tool where the result format is the whole point, these are material gaps.

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 compensate. It usefully expands the bare "json"/"svg" enum by explaining that svg means "standalone inline-SVG HTML," which is genuine added meaning. However, the required "model" parameter (a string up to 1,000,000 chars) is left ambiguous — is it a model ID or the serialized model payload? — which is a significant omission an agent could get wrong.

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 specific verb ("Export") and resource ("supplied model") plus the output formats, which cleanly separates it from the model_create/model_update/model_validate/model_get siblings. It stops short of naming those siblings or describing the export result, but an agent can identify the tool's job from the sentence.

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?

There is no when-to-use or when-not-to-use guidance, no prerequisite that a model must exist or be validated first, and no instruction on how to choose between the two formats beyond listing them. Usage is inferred from the verb "Export" alone.

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