ensp_parse_topology_b64

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

No annotations are provided, so the description must carry behavioral disclosure. It does add real context: the input format is a standard base64 string and the output mirrors ensp_parse_topology (a meaningful promise of shape parity). It says nothing about invalid-base64 handling, size limits, or that this is a non-mutating parse, leaving notable behavioral gaps.

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 very short sentences: purpose first, input format second, return contract third. No filler, no repetition of the name, and the most decision-relevant fact (base64 upload, same result as ensp_parse_topology) is front-loaded.

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?

An output schema exists, so return values need not be described, and the description correctly delegates to ensp_parse_topology for structure. Input format and call context are covered. The omissions worth noting are error behavior for malformed base64 and the untouched 'name' parameter, which keeps it from a 5.

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 0%, so the description is the only source of parameter meaning. It explains content_b64 ('输入是标准 base64 字符串') but never mentions the 'name' parameter or its 'uploaded' default, so half the parameters remain undocumented in both schema and description.

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+resource ('解析 base64 编码的 .topo 字节') and explicitly ties itself to the sibling ensp_parse_topology by saying it returns the identical structure. The parenthetical '(用于 MCP 客户端直接上传)' gives the distinguishing scenario. It stops short of a crisp one-line 'this is the base64 input variant of X', which would make it 5.

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 parenthetical 'for MCP clients uploading directly' implies the usage context and indirectly signals the split from ensp_parse_topology (file-path variant). However, there is no explicit when-to-use/when-not statement and no direct naming of the alternative the way a strong definition would route the agent.

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