serp_scene_info

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

No annotations exist, so the description must carry the full burden; 'Get' implies a safe read but read-only semantics and cost on large scenes are never stated. It does add real context by disclosing that user_text keys/values are included and that mutation belongs to the setusertext command.

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, front-loaded with the verb and resource, with the payload contents listed immediately. The nested parenthetical is dense but every clause carries information; nothing is padded.

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?

An output schema exists, so return structure need not be repeated, and the description nonetheless summarizes the returned categories. It stops short of noting preconditions (an open document) or whether results are expensive to gather, which is the only remaining gap for a zero-argument read tool.

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?

Zero parameters, so the baseline is 4 by rule. The description still adds meaning by explaining where the returned user_text values originate (from setusertext), which is beyond any schema field.

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?

States a specific verb ('Get') and resource ('the current scene') and enumerates the returned contents (objects, layers, selection, bounds, display mode). It does not explicitly differentiate from the overlapping sibling serp_layers or serp_select, which keeps it at 4 rather than 5.

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 is implied (inspect scene state before acting) but never stated as a when-to-use rule, and the exclusion is only partial: 'Set user text with the setusertext command' routes mutation away, but nothing tells the agent when to prefer serp_layers or serp_select over this.

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