chimera_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. It states the tool is safe and automatically called by the Stop hook, but does not detail side effects, mutability, or behavior with different parameters. Given the lack of annotations, this is adequate but not rich.

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 two sentences with no wasted words. The first sentence lists outputs, the second provides safety and usage notes. It is front-loaded and each sentence adds value.

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 simple reporting tool with only two parameters (both with defaults) and no output schema, the description covers the essential aspects: what it returns, when to call it, and that it is safe. It could be improved by mentioning the output format, but it is largely complete.

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 description coverage is 0%, and the description does not explain the 'namespace' or 'include_dedup' parameters at all. It only lists outputs. The description adds no meaning beyond the schema, leaving the agent unable to determine what these parameters control.

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 tool provides an 'End-of-session summary' listing specific items (tokens saved, dedup cache hits, top compressed responses, lock state). This is a distinct verb-resource combination that differentiates it from siblings like chimera_audit or chimera_dashboard.

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 says 'Safe to call any time; the Stop hook calls it automatically when the agent stops responding.' This gives clear context on when to use it (any time) and a caveat about automatic invocation. It does not explicitly exclude alternatives, but the guidance is sufficient for basic use.

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