splat_search

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

With no annotations, the description carries the full behavioral burden and does not say whether an API key or auth is required, whether results are paginated or capped, whether download URLs/licensing are included, or whether 'downloadable' means the tool returns files or merely links. It discloses only that the source is Sketchfab and the asset type is Gaussian splats.

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?

A single front-loaded sentence with the action, source, and content type, and no filler. Nothing to trim.

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?

An output schema exists, so return-value explanation is not required, but for a search endpoint the description still omits pagination behavior, result limits, auth requirements, and what 'downloadable' means operationally — all of which an agent needs to call and interpret it correctly.

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?

One parameter (q) with 0% schema description coverage and a default of 'gaussian splat', yet the description never mentions the query parameter, its default, expected syntax, or how to narrow by tags, licenses, or format. The only usable hint — that the search is inherently scoped to Gaussian splats — is implicit.

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 gives a specific verb (Search) plus a named resource (Sketchfab) and a constrained content type (downloadable 3D Gaussian Splat models), so the agent knows exactly what corpus is being queried. Sibling tools are all geospatial/intel endpoints, so no same-domain disambiguation is needed; the only gap is that 'downloadable' could be clarified as a filter versus a returned field.

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 statement of when to call this versus anything else, no prerequisites, and no note on whether it is the only path to splat assets or part of a two-step download flow. The wording implies a search action but leaves all usage conditions to inference.

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