Returns LLM-optimized instructions for generating Trident diagrams, including quick reference, critical rules (especially Y-axis!), spacing guidelines, common patterns, color conventions, and error prevention checklist. Use this before generating any Trident diagram.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already convey readOnlyHint=true and openWorldHint=true, indicating a safe, non-mutating informational tool. The description adds behavioral context by noting the output is 'LLM-optimized' and listing the specific content domains, which helps the agent anticipate the response nature beyond the raw annotation flags.
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?
The description is a single, front-loaded sentence that efficiently enumerates the included sections without unnecessary filler. Every clause adds value, and the imperative 'Use this before generating any Trident diagram' is a clean closing guideline.
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 read-only guide tool with no parameters and no output schema, the description fully covers what the tool returns and when to use it. The tool's simplicity does not require additional return-value documentation, and the guidance is sufficient for agent selection.
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 has zero parameters, so the schema provides no burden. The description adds no parameter semantics, but with no parameters, a baseline of 4 is appropriate per the rubric (0 params = baseline 4).
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 clearly states the tool returns LLM-optimized instructions for generating Trident diagrams, with an explicit inventory of content (quick reference, critical rules, spacing, patterns, colors, checklist). This specific verb+resource combination distinguishes it from sibling guide tools like get_quick_start and get_trident_spec by emphasizing its role as a comprehensive pre-generation reference.
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?
The description explicitly directs when to use the tool: 'Use this before generating any Trident diagram.' This is a clear usage context, though it does not mention alternatives or when not to use it, which would be needed for a perfect score.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a clearly distinct purpose: CRUD operations for nodes, containers, connections, and annotations are separated, and read-only/utility tools like open_document, get_document_summary, and explain are well-differentiated. No two tools have overlapping functionality.
All tool names follow a consistent verb_noun pattern in snake_case (e.g. add_node, delete_connection, get_document_summary). Even utility tools like open_document and validate_trident adhere to this pattern, making the set predictable and easy to navigate.
With 22 tools, the server is slightly above the typical well-scoped range (3-15). Each tool serves a specific purpose, covering CRUD for diagram elements, multiple read operations, and collaboration features, but the count feels a bit heavy for a focused diagramming tool.
The tool set provides comprehensive CRUD for core elements (nodes, containers, connections, annotations), multiple read methods, guides, and collaboration aids. Minor gaps exist: no bulk operations, no tool to create or manage documents themselves, but the core editing workflow is well-covered.