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

With no annotations provided, the description assumes the full burden of behavioral disclosure. It clearly specifies the content returned (taxonomy, six-source rule, editorial passes, translation policy) and its role in interpretation. It does not mention side effects or return format, but for a read-only informational tool this is adequate and adds meaningful context beyond a simple 'get method' label.

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?

Two sentences, highly efficient. The first sentence delivers the core purpose and lists the specific content areas. The second sentence provides the usage directive. Every word earns its place, and the key information is front-loaded.

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 the absence of an output schema and parameters, the description fully covers what the tool returns and why to call it. It enumerates all major components of the methodology and gives the agent a clear reason to use it alongside the sibling tools. No significant gaps remain.

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, so the baseline is 4. The description adds meaningful context about the fixed scope of the output, which is useful. No parameter documentation is needed because there are none.

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 the explicit verb 'Return' and names the exact resource: 'Wheel of Heaven editorial methodology.' It goes further to enumerate the taxonomy levels and the six-source rule, making it unmistakably distinct from sibling tools that retrieve entries, passages, or sources.

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 clearly states when to use this tool: 'Call this to understand how to weigh everything else this server returns.' This provides a strong usage context. It doesn't explicitly mention when not to use it, but it implicitly positions itself as the foundational reference tool among siblings, so the guidance is reasonably complete.

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