sketchfab_import

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

Annotations already cover the readOnly/idempotent/destructive profile. The description adds that the source must be 'downloadable' and that the operation affects the 'current project'. It does not state what project state changes occur, e.g. whether a new asset is created or how license data is handled, so the behavioral value beyond annotations is modest.

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 one sentence with no filler, starts with the action, and conveys the core operation immediately. It is appropriately concise for the amount of information it attempts to deliver.

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?

At 25% schema description coverage and no output schema, the description must carry much more weight. It covers only the source and target of the operation, leaving parameter semantics, side effects, and relationship to sibling import/asset tools unspecified. This is a meaningful gap for a tool with four parameters and no structured return 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?

Input schema description coverage is only 25%, and the description does not compensate. uid, name, license, and license's nested fields have no semantic explanation in either schema or description. An agent cannot tell what uid refers to, what name should be, or why the license object is required.

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 states a specific action ('Import'), a resource ('downloadable Sketchfab model') and a target ('current project'), making the primary purpose clear. It does not explicitly call out sibling differentiators, but the verb/resource combination distinguishes it from search/get-style siblings.

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 phrase 'downloadable Sketchfab model' and 'into the current project' imply when the tool applies, but there is no explicit comparison to alternatives like my_assets_import, store_download, or download_asset. An agent must infer the intended use case rather than being told when to prefer it.

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