project_painting_read

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

No annotations are provided, so the description carries the full burden. Saying 'Read' discloses a non-mutating operation and it names the paint-data types, but it does not mention permissions, pagination behavior (despite limit/offset existing), or whether the read requires a specific project state.

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?

It is a single front-loaded sentence with no filler. The brevity is appropriate, though because the sentence is the whole description it is under-specified rather than fully structured.

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 five-parameter tool with 0% schema coverage and no annotations, the description is too thin. The output schema covers return values, but the description still leaves the required inputs and paging semantics unexplained.

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% across all five parameters. The description does not explain source, object_id, limit, offset, or member, so the two required parameters and the pagination controls are left undocumented.

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-resource pair ('Read' + painting data) and enumerates the data categories returned: triangle IDs, indices, and support/seam/material/fuzzy paint trees. It is clear what the tool does, though it does not explicitly distinguish itself from project_painting_write or project_geometry_read.

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 guidance on when to use this tool versus alternatives such as project_geometry_read or project_objects_read, nor any mention of prerequisites like needing a loaded project. The read-only intent is implied by 'Read', but the agent must infer the rest.

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