export_diagram_json

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

With no annotations provided, the description carries the burden of disclosure. It states the core behavior (export as JSON with metadata) but does not explicitly clarify that the operation is read-only or describe the exact structure of the returned JSON. This is adequate for a simple export, but lacks explicit safety reassurances.

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, focused sentence that efficiently conveys the tool's purpose and output format. There is no redundant or filler language, making it appropriately concise.

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 simple tool with one parameter and no output schema, the description is mostly sufficient, but it leaves out details about the JSON structure and error conditions. It does not explain what 'full metadata' entails, which might be important for an agent to interpret the returned data.

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 only parameter, filePath, has a schema description covering 100% of its purpose (path to .monopic or .monojson file). Since schema coverage is complete, the description adds no additional parameter details, which justifies the baseline score of 3.

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 identifies the verb (Export), resource (Monodraw diagram), and scope (full metadata as structured JSON). It differentiates from the sibling tool 'export_diagram' by specifying the output format and inclusion of metadata, which implies a distinct use case.

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 implies the tool is for exporting diagrams in JSON format, but it does not explicitly state when to use it over alternatives like 'export_diagram' or 'list_diagrams'. No exclusions or alternative recommendations are provided, so usage context is only implied.

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