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

Annotations are all false/neutral, and the description adds no behavioral context such as side effects, required permissions, or impact on existing entities. The description simply states the action without disclosing any behavioral traits beyond what the name implies, so it provides minimal value.

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 extremely short (three Chinese characters) but is under-specified rather than concise. It does not earn its place because it merely repeats the tool name, and the brevity comes at the cost of clarity and utility.

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 tool with nine parameters, a nested position object, and no output schema, a one-word description is completely inadequate. It fails to explain what an ellipse represents in this geospatial context, how parameters like extrudedHeight or outlineColor work, or how this tool fits among the many sibling shape tools.

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 low at 33%, with descriptions only for material, semiMajorAxis, and semiMinorAxis. The description text itself says nothing about parameters, and the schema is left to carry the burden for the remaining six properties, which have no descriptions. This fails to compensate for the low coverage.

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 ellipse) simply restates the tool name 'addEllipse' in another language, providing no additional specificity or differentiation from sibling add* tools such as addRectangle or addPolygon. This is a tautology that does not clarify the tool's purpose beyond its name.

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 offers no guidance on when to use this tool versus alternatives. There is no mention of prerequisites, use cases, or scenarios where addEllipse would be preferred over other shape-adding tools, leaving the agent without direction for tool selection.

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