list-drawings

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

No annotations are provided, so the description carries full burden. It explicitly states 'Read-only', which is a key behavioral trait for a listing tool. It also implies no filtering by saying 'List every Drawing on a scene', which informs the agent about data volume and scope.

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?

A single sentence that is front-loaded with the action and resource, then efficiently lists all returned fields. No unnecessary words or redundancy. Every part earns 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?

Given the tool's simplicity (one parameter, no output schema), the description is comprehensive. It explains what the tool lists, the fields returned, its read-only nature, and its role in a sequence with update/delete. No gaps remain.

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 coverage is 100%, so baseline is 3. The description does not add any additional meaning beyond the schema's description of sceneIdentifier. The parameter's purpose is already clear from the tool name and schema.

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 clearly specifies the verb 'List' and the resource 'Drawings on a scene'. It enumerates the exact fields returned (id, origin, shape type, dimensions, etc.), distinguishing it from sibling tools like update-drawings and delete-drawings by noting its role as the 'inspect step' before those.

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?

Explicitly states 'the inspect step before update-drawings / delete-drawings', giving clear guidance on when to use this tool and pointing to alternative tools for subsequent mutations. Also declares it is 'Read-only', which helps the agent decide safety.

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