Read a KNOBE document

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

Annotations already indicate read-only, idempotent, non-destructive. Description adds valuable context: returns markdown report, body truncated at 25000 chars, and warns that content is untrusted. No 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?

Front-loaded with purpose and behavioral notes, followed by parameter and return description. Efficient but slightly repetitive between description and Args section. Good overall structure.

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 low parameter count, existing output schema, and annotations, the description provides complete guidance: return format, truncation, untrusted warning, and side-effect guarantee. No gaps.

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?

Only one parameter (path) with full schema coverage. The description repeats the schema's description in the Args section, adding little extra meaning beyond structure. Baseline 3 is appropriate.

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 title and description clearly state the tool reads a KNOBE document, specifying components (verification report, sealed payload, body text). It distinguishes clearly from sibling tools like knobe_seal_* and knobe_verify.

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 states it is for presentation, read-only, and never prompts the user. Warns about untrusted content. However, it doesn't explicitly compare with siblings or give when-not-to-use guidance.

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