akb_drill_down

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

Describes return structure (sections with heading paths) and filter behavior, but lacks details on error handling (e.g., section not found) or confirmations of no side effects. Since no annotations exist, more transparency would benefit.

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 crisp sentences: one stating function and output, one providing usage guidance. No unnecessary words, 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?

For a simple read tool with two parameters and no output schema, the description covers purpose and usage adequately. Could benefit from explaining the L3 hierarchy or document structure context, but it's sufficient for effective 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?

Input schema has 100% coverage with clear descriptions for both parameters. The tool description does not add new parameter information beyond what the schema already provides, so baseline score applies.

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?

Clearly states it retrieves section-level (L3) content of a document, specifying the resource and scope. Differentiates from siblings like akb_get (full document) and akb_browse (perhaps higher-level).

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?

Explicitly advises using it to read specific parts without loading the entire document, giving clear context. Could improve by naming alternative tools for full document retrieval, but current guidance is effective.

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