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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states that the tool returns a guide (a read-only action), and it explicitly discloses that the output is intentionally lightweight and does not attempt to replace the agent's standing instructions. This manages expectations about scope and authority. It could go further by explicitly stating that it has no side effects, but the 'Return' phrasing makes that evident.

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, and every sentence adds value. The first sentence states what the tool does, and the second provides essential context about its design philosophy. There is no fluff or redundant information.

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?

This is an extremely simple tool with zero parameters and an output schema present (per context signals). The description covers the purpose, the nature of the output (short, optional guide), and its limitations. Given the low complexity and enriched structured context, the description is complete. It does not need to detail return format because the output schema handles that.

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 tool has zero parameters, and the schema description coverage is 100% (trivially). According to the rubric, the baseline for 0 params is 4. The description does not need to explain parameter semantics because there are none, and it does not attempt to invent any. It fully matches the baseline.

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 purpose: 'Return a short, optional usage guide for agents integrating with OpenAkashic.' It identifies a specific verb ('Return') and resource ('usage guide'), and it distinguishes itself from all sibling tools by focusing on guidance rather than data operations. The additional notes about being lightweight and non-replacement further clarify its unique role.

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: it is optional, lightweight, and intended as a nudge toward read/write paths without replacing broader standing instructions. This gives the agent clear context for when to use it (for quick orientation) and when not to rely on it (as a comprehensive guide). However, it does not explicitly name alternatives or provide an exhaustive when-not-to-use list, so it falls just short of a 5.

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