kb

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

No annotations provided. Description implicitly distinguishes read vs write operations (e.g., 'pageGet' vs 'pageCreate') but does not explicitly state safety, side effects, or rate limits. Adequate but could be more explicit.

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?

Very efficient: overview sentence, then instruction to use 'list', then compact table of common methods with parameter syntax. Every sentence is informative, no redundancy.

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 no output schema and complex inner methods, description covers discovery (use 'list') and common methods. Lacks explicit return value or error descriptions, but 'list' fills gaps. Mostly complete.

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 100% on method and params. Description adds substantial meaning: explains method values (camelCase verbs, 'list'), and lists detailed parameters for each common method, far exceeding 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 'knowledge base' operations including collections, pages, search, upload. Specific verbs like 'list', 'create', 'pageCreate' define purpose exactly. Distinguishes from siblings by being a multi-method API facade.

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?

Provides detailed usage pattern: call with method and params, use 'list' to get full schemas. Lists common methods with required/optional parameters. Does not compare to sibling tools, but they are unrelated.

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