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

The description discloses the return shape in useful detail — it tells the agent the response bundles settings AND sprites, which is behavioral information the schema does not carry. However, 'Read-only' merely restates the readOnlyHint annotation and adds nothing, and there is no mention of error behavior for a nonexistent project_id. Adequate but partly redundant with the annotations.

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 very short sentences, front-loaded with the returned content. No waste, though the trailing 'Read-only.' sentence duplicates the annotation rather than earning 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 single-parameter read tool with readOnlyHint/openWorldHint annotations and no output schema, the description does the important work of enumerating what is returned. The main omissions are project_id format and not-found behavior, which are minor at this complexity.

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 carries the burden — yet it never explains the expected form of project_id (ID vs slug, where to obtain it). 'One project's settings' only weakly implies the parameter's role. With only one parameter the gap is small, but it is still unaddressed.

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?

Names the resource precisely and enumerates exactly what comes back: settings fields (name, style, description, light, outline, palette) plus sprites. The singular framing distinguishes it from list_projects, though the sibling is never named and the verb ('get') is only implied by the tool name.

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 use this versus list_projects (all projects) or list_sprites (sprites elsewhere). The description does not say that the embedded sprites overlap with list_sprites, nor what prerequisites exist beyond a valid project_id. Only weak implied usage from the word 'One'.

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