pt_topology_png

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

Annotations already flag destructiveHint=true and readOnlyHint=false, and the 'optionally save it' phrase explains why a read-like tool can mutate disk (overwriting an existing PNG). Beyond that, the description omits prerequisites (e.g., whether an open workspace/network is required), what happens when path exists without overwrite, and characteristics of the returned image.

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?

Two short clauses with the primary behavior front-loaded and the optional save noted second; no filler. Minor deduction for the vague 'native workspace' phrasing, which spends words without adding precision in English.

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 zero-required-parameter tool with full schema coverage, annotations, and no output schema, the description covers the essential contract: it returns image content and can write a file. Missing only prerequisites and overwrite-failure semantics, which for this simple an interface are small gaps.

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 description coverage is 100% — both path and overwrite are documented with constraints (parent must exist, replace existing PNG). The description adds only the high-level 'optionally save' framing, which maps to the same parameters but contributes no syntax or format detail beyond the schema; baseline 3 applies.

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 action plus output format (return a PNG as MCP image content) and the optional save behavior, which is enough to tell it apart from siblings like pt_save_network or pt_show. The English text says 'native workspace PNG' rather than explicitly naming it as the topology diagram, leaving a small ambiguity that the tool name and the Chinese half resolve.

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?

There is no explicit when-to-use, prerequisite, or alternative guidance; the usage is only implied by the name and the 'optionally save it' clause. No sibling does the same job, so the risk of confusion is low, but the description does not tell the agent under what conditions to reach for this tool.

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