booboo_stats

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

The description discloses that output is broken down by layer, but with no annotations provided, it lacks details such as whether the operation is read-only, what happens if the graph is empty, or any rate limits. The description carries the full burden but is not exhaustive.

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 sentence that is concise, front-loaded, and contains no superfluous words. 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?

Given that the tool has no parameters and no output schema, the description is fairly complete. It tells the user exactly what the tool returns: node/link counts per layer. A minor addition would be whether totals are included, but it is adequate.

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 and schema coverage is 100% (vacuously). The description adds no parameter information, which is acceptable because there are no parameters to document. Baseline for 0 parameters is 4.

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 that the tool provides node and link counts for the entire graph, broken down by layer. This specific verb+resource combination effectively distinguishes it from siblings like booboo_neighbors, booboo_node, booboo_path, and booboo_search.

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 when overall graph statistics are needed, but it does not explicitly state when to use this tool versus alternatives or provide any exclusions.

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