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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered; the description adds the useful behavioral context that this is a static reference loadable ahead of bulk generation versus an in-session editing flow. It does not describe size or format of the returned content, so it stops short of full transparency.

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 what is returned and then the usage constraint. The 'especially Y-axis!' parenthetical is informal but signals a genuinely high-value rule; every sentence earns its place with no 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 carries the burden of explaining the return value, and it does so by enumerating the guide's sections. For a parameterless read-only reference tool, the definition is complete enough to select and invoke correctly.

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 there is nothing for the description to disambiguate; baseline 4 applies. No parameter claims are made that conflict with the empty schema.

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 LLM-optimized instructions for generating Trident diagrams' — and enumerates the content (quick reference, rules, spacing, patterns, colors, checklist). It does not explicitly distinguish itself from sibling guide-like tools such as get_quick_start, get_trident_spec, and get_comprehensive_example, which leaves some ambiguity about which reference to load.

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 states when to use it ('before generating Trident markup'), when it is not needed ('not needed up front in a live session that edits a document'), and names the alternatives (add_node / add_connection). It even scopes the exception case to domain conventions (BPMN/UML/flowchart, ERD, C4).

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