browse_tree

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

With no annotations provided, the description must fully disclose behavior, but it only says 'browse.' It does not explain that the tool likely returns a hierarchical structure, respects max_depth, or any side effects (none expected). The agent gains no insight into what happens during invocation.

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, short sentence that gets to the point quickly with no filler. However, it is so concise that it sacrifices necessary detail; it could be expanded while remaining efficient.

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 a simple tool with two parameters and no annotations or output schema, the description should at least explain what 'browse' means (e.g., 'list immediate children up to a depth'). The current description leaves the agent guessing about the tool's behavior and output.

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 description mentions 'by node id,' hinting at the 'node_id' parameter, but it ignores 'max_depth' entirely. With 0% schema description coverage for both parameters, the description adds minimal semantic value beyond the schema field names.

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 states the verb 'Browse' and resource 'wiki tree' with the key parameter 'node id,' making the basic purpose clear. However, it does not specify what 'browse' returns (e.g., children, subtree) or how it differs from similar tools like 'get_tree_path' or 'search_in_subtree,' so it lacks full differentiation.

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?

No guidance is provided on when to use this tool versus alternatives. The description does not mention use cases, prerequisites, or when not to use it, leaving the agent without decision-making context.

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