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

With readOnlyHint/openWorldHint already covering safety, the description still adds real behavioral context: the highest-cost errors are silent (content written but never displayed, blocks off-screen, wrong cap-table percentages) and nothing raises an exception. It also warns the topic-less read is voluminous, which sets output-size expectations.

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?

Purpose and usage lead, with the silent-failure rationale and argument behavior following in a logical order. The parenthetical examples in the middle sentence are a little dense, but each clause carries information rather than filler.

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 must convey what comes back: it frames the return as prose rules organized by kind and topic and flags the volume of the unfiltered read. That is sufficient for an agent to decide to read it before writing, though the actual structure of the returned rules is left implicit.

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 description coverage is 100% and both parameters carry enums with their own explanations, so the schema does the heavy lifting. The description's 'Without arguments, returns the cross-kind rules / with topic restricts' largely restates the schema rather than adding new syntax or format meaning, so the baseline 3 is appropriate.

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?

States a specific verb and resource — returns the OrgGen 'manual' (rules) for a diagram kind — and scopes it further (cross-kind rules without arguments, single topic with 'topic'). It is clearly distinguishable from the write siblings and from get_schema_overview, which it explicitly names as a different lookup.

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 is read before a first series of writes on a kind not yet handled' gives a concrete trigger condition, and the schema notes that a kind's playbook is useless without matching the project's kind read via get_schema_overview. It never states an explicit 'do not use' case or names a true alternative tool, so it stops 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.