get_scene_info

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

With no annotations, the description must carry all behavioral disclosure. It indicates what data is returned, implying a read-only operation, but does not explicitly state that it has no side effects or specify the exact return format. It is adequate but could be more explicit about its read-only nature.

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?

A single, compact sentence that front-loads the main purpose and lists exactly what is retrieved. There is no extraneous text, every word earns its place.

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?

For a parameter-less query tool, the description fully communicates the returned values (units, frame rate, frame range, object count). There is no output schema, but the description lists the return items explicitly, so an agent knows what to expect. Nothing essential is missing.

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?

The tool has zero parameters, so the schema is trivially complete. The baseline for 0 parameters is 4, and the description does not need to add parameter-level detail since there are none.

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 action ('Get') and the specific resource ('scene info') with enumerated data points (units, frame rate, frame range, object count). This precisely distinguishes it from siblings like 'list_objects' or 'get_selection', which target different data.

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 implies usage for retrieving scene-level metadata, and the tool's name and parameter-less nature make its purpose self-evident. However, it does not explicitly state when to use it versus alternatives or mention any exclusions, though for such a simple tool this is not a significant gap.

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