add_element

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'add element,' implying a mutation but not explaining that it modifies an existing diagram, whether it is reversible, permission requirements, or potential errors. This is minimal and insufficient.

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 concise sentence that is front-loaded with the core purpose. It contains no redundant or unnecessary words, and the brevity is appropriate for a straightforward action.

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?

Given the nested element schema and no output schema, the description should provide more context about what an element is, valid element types, or the requirement that the target diagram already exists. The one-sentence description leaves critical gaps for an agent to fully understand the tool's operation.

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 input schema already describes both parameters (diagram_id and element), so schema coverage is 100%. The tool description adds no further meaning beyond the schema, meeting the baseline but not enhancing understanding of nested properties like type or position.

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 '向图表添加元素' ('Add element to diagram') clearly states the specific action (add) and resource (element to a diagram). It distinguishes itself from sibling tools like delete_element and update_element by conveying the operation's scope.

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 provides no guidance on when to use this tool versus alternatives such as create_diagram or create_flowchart, nor does it mention prerequisites like the diagram existing before adding elements. There is no explicit usage context or exclusions.

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