get_scene_schema

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 only states the return type and version, without disclosing any behavioral traits such as auth requirements, side effects, or rate limits. For a read-only tool without parameters, this is minimal but adequate for basic use.

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 with zero waste. Every word earns its place: 'Return', 'discriminated JSON schema', 'for scene IR version 2'. It is front-loaded and appropriately sized.

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 zero parameters and the presence of an output schema (context indicates has_output_schema=true), the description is sufficient. It does not need to explain return values as the output schema covers that. However, it could be improved by noting that it requires no arguments or permissions.

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?

There are no parameters, so baseline is 4. The description adds meaning by specifying 'discriminated JSON schema' and 'version 2', which clarifies the output format beyond the empty input 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 states the tool returns a 'discriminated JSON schema' for 'scene IR version 2', which is a specific verb+resource combination. It distinguishes from sibling tools like 'get_scene' and 'list_scenes' which deal with scene data, not schemas.

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?

No explicit guidance on when to use this tool vs alternatives, but the context implies it is the only tool for retrieving the schema. The description lacks when-to-use or when-not-to-use instructions.

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