list-scenes

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

No annotations are provided, so the description carries the full burden. It states the tool lists scenes and specifies returned fields, implying a read operation. However, it does not explicitly declare it as read-only or disclose any other behavior (e.g., pagination, ordering, default 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?

The description is a single sentence that efficiently conveys the tool's purpose and key features. It is front-loaded with the primary action and resources. Minor improvement could be breaking into two sentences for readability, but current structure is concise and clear.

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 list operation with no output schema, the description adequately covers the returned fields and filtering options. It does not mention ordering, pagination, or default behavior (e.g., returns all scenes by default), but those are not critical given the tool's simplicity. Overall, it provides sufficient context for an agent to use the tool effectively.

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 100%, so the baseline is 3. The description mentions both parameters ('filter by name substring', 'show only the active scene') but adds no new semantics beyond what the schema already provides (e.g., case-insensitivity, default values).

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 specifies the verb 'List' and resource 'Scene documents', and enumerates the returned fields (id, name, active flag, etc.). This clearly distinguishes it from sibling tools like create-scene or get-current-scene.

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 mentions optional filtering (by name substring or active scene only), implying when you might use these options, but provides no explicit guidance on when to use this tool versus other scene-related tools. It lacks 'when to use' and 'when not to use' context.

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