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

Annotations already establish readOnlyHint=true, idempotentHint=true and closed-world access, so the safety profile is covered. The description adds two pieces of context beyond that: results carry 'live counts' (freshness) and single-node retrieval is uncapped. It does not describe pagination, size limits, or the shape of the aggregate result.

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, zero boilerplate, and the default behavior (full structure) is front-loaded before the optional override. The 'DNA double helix' phrasing is evocative rather than informative and slightly dilutes the opening, keeping it from a 5.

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 single-parameter read-only tool with no output schema, the description covers the call surface adequately, but it leaves the return shape ambiguous — an agent cannot tell what fields a node's 'covenant, stakeholder and implementation rules' actually contain, and there is no output schema to fall back on.

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 is 100%, so the baseline is 3, but the description genuinely enriches the terse schema text: it explains that `node` returns that node's covenant, stakeholder and implementation rules, which the schema only calls 'one node's detail'. It also implicitly contrasts with the whole-architecture mode.

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 names a concrete resource — the Mzizi architecture ('DNA double helix' of nodes, rungs and strands) with live counts — and distinguishes the two modes (whole structure vs. a single node's detail). The metaphor is unusual but the returned artifact is identifiable, and the `node` branch is spelled out. It stops short of cleanly defining what 'nodes/rungs/strands' are, so it is not a textbook 5.

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 implicitly gives a routing rule: omit `node` for the full architecture, pass `node` for one node's covenant/stakeholder/implementation rules. That is a real when-to-use signal for the parameter. However, it says nothing about when to prefer this over sibling tools like mzizi_get_doctrine or mzizi_get_component, and gives no exclusions.

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