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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the description only needed to add context — and it does, disclosing the API-key authentication requirement and the JSON shape (taskId, taskType, title, thumbnail). It does not discuss throttling or what happens past the default result cap.

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?

Two sentences, no filler: the first defines scope and return shape, the second gives the use case and the auth prerequisite. Front-loaded and every clause earns its place.

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 simple zero-required-param read tool, this covers everything an agent needs: what is returned, why to call it, and the API key requirement, with annotations handling the safety profile. No output schema exists, but the description lists the return fields itself.

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 100%, so the single `limit` parameter (default 50) is already fully documented in the schema, and the description adds nothing about it. Baseline 3 applies when the schema does all the parameter work.

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 and resource ('List the 3D models on your Waspes account'), names the two sources (3D Studio and Waspex), and enumerates the returned fields. No sibling tool lists models, so the resource alone separates it from the generate_*/send_to_roblox tools.

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?

'Use it to see what can be imported into Roblox Studio or downloaded' gives a clear trigger for calling it. It stops short of naming an alternative or stating when-not to use it, but with no competing list tool in the sibling set there is little ambiguity left.

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