Persist a specific diagram immediately by saving it to disk via its ID, ensuring changes are written without waiting for automatic sync.
Force an immediate sync of a specific diagram to disk.
Args: diagram_id: ID of diagram to save
Returns: dict containing success status
| Name | Required | Description | Default |
|---|---|---|---|
| diagram_id | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must carry the full burden. It states that it forces a sync to disk, implying a write operation, but does not disclose whether it overwrites existing files, requires permissions, or what happens on failure.
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?
Front-loaded with the action, and the Args/Returns structure is compact. However, the Returns line duplicates information already available in the output schema, slightly reducing efficiency.
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 write tool with no annotations, the description is incomplete. It lacks prerequisites, side effects, and usage context, leaving the agent under-informed for safe invocation.
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 coverage is 0% and the only parameter description is 'ID of diagram to save', which adds little beyond the parameter name. No format, source, or lookup guidance is provided.
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: syncing a specific diagram to disk, with the qualifier 'force an immediate' that implies urgency. This distinguishes it from load/create/delete siblings, though it does not name them explicitly.
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?
No guidance on when to use this tool versus alternatives such as diagram_create or diagram_load. The agent must infer that it is for persisting an existing diagram, but no conditions or prerequisites are given.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.