kb_page_content

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

With no annotations provided, the description carries the transparency burden. It discloses that the tool fetches blocks and concatenates them into full text, offers format options (markdown/text/html), and requires the 'landing' webhook permission. This is meaningful behavioral context, though it omits error handling and explicit return type.

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 two sentences, front-loaded with the core purpose, then the method, format choices, and permission requirement. Every sentence contributes useful information without redundancy or fluff.

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 relatively simple tool with no output schema, the description covers the essential aspects: what it does (full text), how it works (concatenates blocks), output formats, and required permissions. It falls short of fully specifying the return structure or edge-case behavior, but is largely complete for practical invocation.

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 schema already describes all three parameters (landing_id, scope, format) with full coverage. The description repeats the default format and the 'from kb_sections' source, but adds no new semantic information beyond the schema. Baseline 3 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?

The description clearly states the tool's function: retrieving the full text of a knowledge base page by its landing_id, collecting and concatenating page blocks. It distinguishes itself from sibling search/document tools by focusing on full-page content extraction.

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?

The description implies usage context (when you have a landing_id and need full page text) and mentions a required webhook right, but it does not explicitly contrast with alternative tools like kb2_document or describe when not to use it. Usage is understood but not strongly guided.

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