booboo_report

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

No annotations are provided, so the description must disclose behavior. It states that reports are durable and immediately queryable, and that they land on the Reports timeline, indicating persistence. However, it does not disclose whether calls are append-only, any authentication requirements, rate limits, or the return value, leaving some behavioral gaps.

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 three concise sentences, with the main purpose front-loaded in the first sentence. It uses a dash to define the report and includes only necessary details about durability, queryability, and timing.

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?

Given the simple interface (3 parameters, no output schema), the description covers the tool's role, placement, and call timing. It could mention the return value or any response, but it doesn't need to for this simple tool. The high schema coverage further reduces the need for parameter explanation.

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 100%, so all parameters are documented in the schema. The description adds a bit of context by linking the report content to 'what an agent just closed,' but does not add significant meaning beyond the schema, so baseline 3 applies.

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 verb 'File a report' and defines it as a plain-English summary of closed work, landing on the panel's Reports timeline. It distinguishes itself from siblings like booboo_remember and booboo_stats by specifying the timeline and session-closing context.

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?

It explicitly instructs to 'Call this as the last act of a session,' providing a clear when-to-use trigger. However, it does not name alternatives or exclusions, though the session-last context implicitly separates it from other tools.

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