Content Root Tree Tool

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds that depth is 'bounded' and results are paginated, which is modest but real context beyond the annotations; however it does not say what happens when depth is null/omitted, what the traversal order is, or any auth/scope constraints.

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?

A single front-loaded sentence with no filler; the core action and its two controlling dimensions come first. It is tight, though the brevity borders on under-specification rather than pure economy.

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 three-parameter tree read with no output schema and zero schema description coverage, the description is thin — an agent still lacks depth/limit/offset semantics and any sense of result shape. The readOnly annotation and the mention of depth and pagination keep it from being wholly inadequate.

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%, so all three parameters (depth, limit, offset) carry no documented meaning in the schema. The description only gestures at the concepts with 'bounded depth' and 'pagination' — it never explains what a null depth means, how limit bounds the tree walk, or how offset interacts with traversal.

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 gives a specific verb ('Read') and resource ('root tree content (from root nodes)'), and the parenthetical scoping distinguishes it from sibling reads like evo.content.children or evo.content.descendants without naming them. It is clear what the tool returns, though it never explicitly contrasts itself with those siblings.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no sibling is named as an alternative for the non-root cases. The phrase 'from root nodes' only implies that this is the top-of-tree entry point; an agent must infer that children/descendants tools exist for deeper traversal.

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