get_scene

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

The description discloses the return content (elements, state, version, session ID) and multi-session capability, adding value beyond the schema. No annotations are present, so it carries the full burden; it is transparent about being a read operation.

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 concise, front-loaded with the main purpose, and uses clear sections. Every sentence adds value without redundancy.

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 no output schema and one optional parameter, the description covers key information: what is returned, when to use it, and session handling. It could be slightly more explicit about being read-only, but overall complete.

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% with a description for sessionId. The description adds context ('Multi-session support: Specify sessionId') but mostly restates the schema's 'If not provided, uses default session.' Baseline is 3 for high coverage.

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 states the tool retrieves complete information about the current diagram scene, with a specific list of return items. It distinguishes from siblings by being a read-only retrieval tool.

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?

Usage scenarios are provided (viewing content, analyzing structure, obtaining IDs for updates/deletion) and multi-session support is mentioned. However, it does not explicitly compare to alternatives or state when not to use.

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