get_session_report

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

No annotations are provided, so the description carries the full burden. The verb 'Fetch' implies a read-only operation, but the description does not explicitly state it is non-destructive or mention requirements like authentication or error behavior. It does add value by specifying what the report contains (status, quality, full report).

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 a single, concise sentence that directly communicates the tool's function without unnecessary words or repetition. It 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?

The output schema exists, so return values are covered, but the description lacks guidance on usage context and parameter semantics. For a simple fetch tool, it is minimally adequate but leaves gaps around prerequisites and sibling tool differentiation.

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?

With 0% schema description coverage, the description must compensate for the parameter `scene_hash`, but it merely restates the parameter name without explaining what a scene hash is or how to obtain it. This is insufficient for an agent to correctly populate the parameter.

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 ('Fetch'), the resource ('session report'), and the scope ('for a scene hash'). It also lists the key content (status, quality, full report), which distinguishes it from sibling tools like list_sessions.

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 clearly indicates the tool is used to retrieve a session report for a specific scene hash. It does not explicitly exclude alternatives or provide when-to-use guidance, but the context is clear enough for an agent to select it when report details are needed.

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