get-scene-dimensions

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

With no annotations, the description fully carries the behavioral disclosure. It explains the padding inset and its implication for placeable pixel calculations ('NOT just gridCell×size'), provides the exact returned fields, and notes that no scene activation is needed. No contradictions present.

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 three sentences, each serving a clear purpose: stating the main function and return values, explaining the padding nuance, and noting the usage context. It is front-loaded with the key action and is free of extraneous words.

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 single parameter and no output schema, the description comprehensively explains what the tool returns and the behavioral nuance about padding. It fully informs an agent about the tool's purpose and output without needing additional schema details.

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 the parameter 'sceneIdentifier' described as 'Scene id or exact name.' The description adds minimal extra meaning by reiterating 'by id or exact name' and adding 'works on any scene,' but does not significantly deepen understanding beyond the 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 it reads a scene's live padded-canvas geometry, specifying exact properties like total width/height, background rect, grid size/rows/columns. This distinguishes it from siblings like 'get-current-scene' which returns general scene data, and 'list-scenes' which lists scenes.

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 indicates the tool is for coordinate math ('feeds the legend→pins cell→px math') and notes that it works on any scene without activation. While it doesn't explicitly contrast with alternatives, the context implies use for geometry calculations, and sibling tools like 'get-current-scene' serve different purposes.

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