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

Annotations already declare readOnlyHint=true, so the explicit 'Read-only' line adds little new information. The description does add useful behavioral context by specifying the 'most liked first' ordering and enumerating returned fields, but it does not address pagination or rate limits; the annotation covers the main safety profile.

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?

The description is a single compact sentence that front-loads the action, resource, ordering, and returned fields. 'Read-only' is a short reinforcement, and there is no filler or unnecessary repetition of schema details.

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 read-only list operation with one optional parameter and no output schema, the description provides the essential return fields, ordering, and public scope. The limit semantics are fully covered by the schema, so the description is sufficient for an agent to call the tool correctly, though it leaves minor ambiguity about how 'most liked' is computed.

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?

The only parameter, limit, is fully documented in the schema with a valid range of 1–20 and a default of 20, so schema description coverage is 100%. The tool description adds no additional parameter-level meaning, which is acceptable given the schema's completeness.

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 uses a specific verb ('Returns') and names the exact resource: drawings on the public wall. It also states the ordering ('most liked first') and lists the returned fields, which clearly distinguishes it from siblings like vote_drawing, submit_drawing, and check_drawing.

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 description clearly defines the intended use case: retrieving public wall drawings. It does not explicitly name alternatives or exclusions, but the read-only framing and sibling list make the appropriate context apparent.

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