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

Although annotations already declare readOnlyHint/idempotentHint/destructiveHint, the description adds meaningful behavioral context beyond the structured data: it performs no transaction, returns composed knowledge as markdown, is identity-free, and notes the specific voice. No contradiction with annotations.

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 first sentence states the main purpose, followed by short, informative sentences covering safety (read-only), return format, and an invocation example. No wasted words.

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 zero-parameter, no-output-schema knowledge tool with strong annotations, the description fully covers what's needed: resource, voice, side-effect profile, return type, identity behavior, and a call example. There is no meaningful gap.

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?

With zero parameters, the baseline is 4, and the description reinforces this with 'Zero-arg; identity-free' plus the explicit example 'call about_us_about with arguments {}.' There is nothing more to add for a zero-arg tool.

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 uses specific language: 'Read About ComOS — the Federation User Manual's knowledge (in the comos-federation voice).' It clearly names the verb (Read), the resource (About ComOS/Federation User Manual knowledge), and the return (markdown). It helps distinguish itself from siblings like how_to_about and federation_why by scoping the exact voice and nature of the knowledge.

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 provides clear context: read-only, performs no transaction, zero-argument, identity-free, and includes a usage example. It does not explicitly name alternatives or give when-not-to-use guidance, but for a static knowledge-read tool, the context is sufficient.

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