akb_browse

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

Discloses slim response default, truncated output, return structure, use of limit/offset, and filter case-insensitivity. No annotations provided, so description carries full burden; it delivers key behavioral traits without contradictions.

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?

Four sentences, no fluff. Front-loaded with core purpose, then key behavioral notes. Every sentence adds value.

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 9 parameters and no output schema, description covers browsing modes, slim response, filter usage, and return structure. Lacks detail on pagination or edge cases but sufficient for typical use.

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 coverage is 100%, baseline 3. Description adds context: explains top-level vs collection browsing behavior, slim response vs include_summary, and deprecation of query parameter. Provides meaning beyond schema.

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?

Description clearly states it browses all vault content (documents, tables, files) and distinguishes behavior with/without collection parameter. Among 42 siblings, no other tool describes browsing vault content at this granularity, making it distinct.

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?

Mentions using filter to narrow by domain keyword, and implicitly when to use collection param vs top-level. No explicit guidance on when not to use this tool vs alternatives like akb_search or akb_drill_down, which are present in sibling list.

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