lint_scene_refs

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

Annotations already indicate readOnlyHint=true, and the description repeats 'read-only', adding little beyond scope. No details on output format, side effects, or what 'lint' produces. The path parameter mention is confusing.

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 brief and front-loaded with the main purpose, but it includes an apparent parameter description (path) that seems truncated and mixes parameter info into the main description. Structure is awkward.

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?

Without an output schema, the description should explain what the tool returns; it doesn't. The inconsistency between the mentioned path parameter and the empty schema makes the tool's usage unclear. For a linter, more context is needed.

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 input schema defines no parameters, yet the description references a 'path' parameter, which is misleading. This actively contradicts the schema and provides false guidance to the agent.

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?

Clearly states it's a read-only linter for scene references in DSL scripts or batch commands. Distinguishes from sibling lint_playtest by specifying the exact domain (scene references).

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?

Gives context on what it lints (scene references) but does not explicitly mention when to prefer this over lint_playtest or other tools. No explicit exclusions or alternatives.

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