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

Annotations already cover readOnly, idempotent, destructive and open-world flags, so repetition of read-only adds little. The description does add real value: it discloses the scope is 'bounded' and issues an explicit authority disclaimer (no publication, mutation, provider-contact or execution authority). It does not specify what the bounded limits actually are, leaving a minor gap.

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, both front-loaded: the capability first, then the sibling routing and authority limits. No filler, no restatement of the title.

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?

With no output schema, the description compensates by enumerating what the overview returns (counts, registries, observation surfaces, provenance). Combined with rich annotations and a zero-parameter schema, nothing needed to call it correctly is missing.

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 takes zero parameters, so the baseline is 4. There are no arguments whose semantics could be clarified or omitted; the schema is trivially complete.

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?

Names a specific verb (read) and resource (a bounded structural overview of the canonical zenitheye.net knowledge graph), then enumerates the contents: node counts, edge count, registries, observation surfaces and provenance. An agent can distinguish it from knowledge_graph_search/node/neighbors without opening any schema.

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?

Explicitly routes the agent: search to locate nodes, node for one exact node, neighbors to traverse edges. Each alternative is named with the condition that selects it, making the choice between the four knowledge-graph tools unambiguous.

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