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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered. The description adds modest extra context (returns artwork that should be visually inspected, SpriteShip fields are flexible metadata) but says nothing about the assetOffset pagination behavior or result size.

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?

Three compact sentences with the primary content front-loaded; the last sentence about SpriteShip metadata is slightly cryptic but plausibly earns its place. No padding or repetition.

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 read-only tool with no output schema, the description usefully enumerates what is returned, which partially compensates. It still omits pagination via assetOffset and the required/optional distinction between projectId and mapId, leaving gaps an agent must guess at.

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% and there are three parameters (projectId required, mapId and assetOffset optional). The description never mentions any of them, so the meaning of mapId scoping and especially the assetOffset pagination cursor is left entirely unexplained despite no schema help.

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 read verb plus the resources it returns (project art, material recipes, limits, shape classes, map JSON, revision), which is far more informative than the title. It does not, however, distinguish itself from close siblings such as map_workbench_context, map_authoring_schema, or get_map_draft, so an agent cannot route between them from the text alone.

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?

It gives downstream workflow advice ('Inspect the returned artwork visually before selecting assets', 'Read your game code to establish movement/mechanics'), which implies this is a first-step reconnaissance call. It never says when to prefer this over the other context/schema tools, nor any preconditions, so usage is only implied.

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