browse_library

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds the genuine behavioral constraint that traversal is incremental (one folder per call), but says nothing about what the listing contains, whether items are loadable, or whether the local browser can change between calls.

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?

Three sentences, front-loaded with the operation, then the root enumeration, then the traversal rule. The root list is long but earns its place since the schema provides no enum; no filler wording.

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?

Without an output schema, the description should say what a listing returns (names, folder vs. loadable item distinction, ordering). It omits this entirely, which leaves the agent unable to interpret results well enough to chain into load_from_library.

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 the description must carry the parameters. It does: it enumerates all twelve valid root values (the schema has no enum at all) and explains that path is a sequence of folder names. The path example "[]" is terse and a concrete non-empty example is missing, keeping it below 5.

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?

"List one level of Live's browser" states a specific verb and resource, and "one level at a time" scopes it. It does not name the adjacent sibling (load_from_library), so the agent has to infer that this tool enumerates rather than loads.

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 real usage guidance in "Navigate one level at a time: add one folder name per call", which tells the agent how to chain calls. It never says when to prefer this over load_from_library, and gives no guidance on what to do with the listing once obtained.

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