sketchfab_get

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

The annotations already declare readOnlyHint=true and openWorldHint=true, so the description does not contradict them. It adds no extra behavioral context beyond 'by uid,' such as response shape, error behavior, or side effects, but for a simple read-only getter this is acceptable and not misleading.

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 short, front-loaded sentence with no filler. Every word contributes to identifying the operation, and the key detail ('by uid') is included upfront.

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 low complexity—one required parameter, read-only annotations, and no nested schema—the description covers the essential information needed to call the tool. It does not describe the return value or not-found behavior, but for a simple get-by-id operation this is a minor gap.

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 input schema only defines 'uid' as a required string with no description. The description's 'by uid' clarifies that this parameter is the lookup key for the model, adding operational meaning. However, it does not elaborate on the expected format or provenance of the uid, though the single simple parameter is largely self-explanatory.

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 a specific verb and resource: 'Get a Sketchfab model by uid.' It identifies the access method (by uid), which distinguishes it from sibling operations like sketchfab_search or sketchfab_import, though it does not explicitly name or contrast those alternatives.

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?

Usage is implied: this tool is for retrieving a model when you already have its uid. However, the description gives no explicit guidance about when to use this instead of sketchfab_search, sketchfab_import, or store_get, and no alternatives are mentioned.

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