Project overview

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

No annotations are provided, so the description carries the full behavioral burden. It discloses one useful trait (geometry is 'verbose') and implies a read-only, non-mutating dump, but says nothing about cost, output size, permissions, or side effects of a large dump.

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?

Two tightly written sentences with the payload scope front-loaded and the usage cue second. No filler or repetition of the title.

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 parameterless-required, read-only inspection tool with no output schema, the description covers what the tool returns and how to toggle it. Missing only the default-on behavior of elements/textures/animations and any note on output volume for large projects.

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 only 25% (just geometry), but the description compensates by enumerating the three optional payload families — element tree, textures, animations — which map onto the elements/textures/animations booleans. It adds real meaning beyond the bare boolean names, though it never mentions that all three default to true.

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?

Names a concrete verb and resource plus the exact payload categories (format, mode, sizes, elements, textures, animations), so an agent knows what comes back. It does not explicitly distinguish itself from near-neighbors like bb_status or bb_list_elements, which is the only thing keeping it off a 5.

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?

'Call this to re-orient after a large edit' gives one positive usage trigger. There is no statement of when NOT to use it and no named alternative (e.g., bb_list_elements for elements alone, bb_status for connection state), so the routing guidance is implied rather than explicit.

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