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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered elsewhere. The description adds one piece of behavior beyond that: the response is an expanded tileset that includes its parts, which tells the agent it doesn't need a follow-up call per part. It says nothing about missing-ID behavior or error handling.

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 short sentence, front-loaded with the verb and resource, with the notable payload detail (parts included) appended. No filler, though it is arguably under-written rather than overly concise.

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 one-parameter read-only lookup with full annotation coverage and no output schema, an agent has everything it needs: what it returns (a tileset with parts) and the key to fetch it by. Nothing essential to correct invocation is missing.

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% for the single parameter, so the description has to carry the meaning. It only confirms that tilesetId is an ID lookup; it does not mention the positive-integer constraint or whether a nonexistent ID throws or returns null.

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 ("Get a tileset") plus the retrieval key (by ID), which is enough to distinguish it from create_tileset/update_tileset. It does not explicitly distinguish itself from list_tilesets or get_default_tileset, so the sibling differentiation is implicit rather than stated.

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 ID-based lookup implicitly signals 'use when you already know the tileset ID, otherwise use list_tilesets', but no alternative or exclusion is named. An agent must infer the when-to-use from the schema's required tilesetId alone.

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