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

Annotations already declare read-only, idempotent, non-destructive, and closed-world behavior, so the description does not need to repeat safety basics. It adds useful context by specifying that only approved KB items are listed, which fields appear, and that pagination metadata includes total, offset, limit, and nextOffset.

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 compact and front-loaded: the core browse/enumerate purpose appears first, followed by usage routing and return shape. Every clause contributes either selection guidance or invocation context.

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?

There is no output schema, but the description documents the returned fields and pagination metadata. With all three parameters fully schema-documented and sibling alternatives named, an agent has enough context to select and invoke the tool correctly.

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 description coverage is 100%, so the baseline is 3 even without additional parameter detail in the description. The description still adds meaning by framing limit/offset/section as paging through a section or the full allowlist and by exposing nextOffset in the return shape.

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 gives a specific verb and resource: 'Read-only browse/enumerate of approved Nebula KB items,' and names the exact item fields returned. It also distinguishes this tool from sibling tools by role: list/browse versus ranked search, full record retrieval, and summary overview.

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?

It explicitly says when to use this tool: to page through a section or the full allowlist. It also routes to alternatives by condition: nebula_search for ranked queries, nebula_section for full record content, and nebula_overview for a summary.

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