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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered structurally. The description adds real value beyond them by disclosing the coupling contract: the returned guideCode is a required input for create_model and edit_model, which changes call sequencing. It stops short of describing the guide's size or format, which is why this is a 4 rather than a 5.

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?

Three sentences, front-loaded with the return value, then the reading trigger, then the downstream dependency. Every sentence carries distinct operational information — the guide's contents, the timing rule, and the guideCode contract — with no restatement of the title or annotations.

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?

There is no output schema, so the description must describe the return value, and it does: the modeling guide plus a guideCode. It also frames the guide's topical sections, which is enough for a zero-parameter documentation tool. An agent knows what it will get, why it needs it, and what to do with the result.

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 input schema has zero properties, so there are no parameters whose meaning could be clarified or obscured; the baseline for a no-parameter tool applies. The description correctly says nothing about inputs, which is consistent and avoids confusing an agent into hunting for optional filters.

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 ('Returns') and resource ('toro4n's guide to Neo4j graph data modeling'), then enumerates the guide's coverage: working with the user, holding a model, naming, and node/property/label/relationship/intermediate-node decisions. That level of enumeration lets an agent distinguish this documentation tool from every sibling (create_model, get_model, list_models, etc.) 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?

Explicit when-to-use: 'Read it before you design a model or review one.' It also names the downstream dependency — create_model and edit_model require the guideCode this returns — which is effectively a prerequisite ordering rule, not just a suggestion. Nothing is left to inference about when this tool is the right call.

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