load_scene_image

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

Adds one behavioral trait: resizing/compressing until data size <= 1MB. However, no annotations exist, so the description carries the full burden. It does not disclose authentication needs, rate limits, error handling, or behavior when compression fails.

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?

Two sentences with no wasted words. The core action is front-loaded. Every sentence adds value: purpose and behavioral constraint.

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?

No output schema, yet description does not specify return format (e.g., base64, URL) or error cases. For a tool with 4 parameters and no annotations, the description is incomplete. It covers basic purpose but omits many usage 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 0%, and the description provides no explanation of parameters. It mentions resizing/compression but does not link to max_width or max_height. The description fails to compensate for the lack of parameter descriptions in 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 returns an image for the player's current story and scene, with resizing/compression. The verb 'Return' and resource 'image for the player's current story and scene' are specific. While siblings are different actions, it doesn't explicitly differentiate or highlight its unique role.

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 guidance on when to use this tool versus alternatives. No mention of context, prerequisites, or exclusions. The description implies it should be used when an image is needed for a scene, but lacks explicit usage direction.

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