search_elements

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

With no annotations, the description carries the full burden, but it only states the action without any behavioral details such as whether hidden/locked elements are excluded by default, whether results are highlighted, or how results are returned. No side effects or permissions are mentioned.

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, clear sentence with no redundant content, making it easily scannable and 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?

Given the tool's complexity (five parameters, nested objects, no output schema), the one-sentence description is grossly insufficient. It lacks information about return values, default search scope (current vs all), result limits, and how filtering works, leaving the agent to infer almost everything from the schema.

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 provides descriptions for all properties including filters, search_options, and sort_options, achieving 100% coverage. The description itself adds no parameter semantics, relying entirely on the schema, so a baseline of 3 is appropriate.

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 '在图表中搜索元素' (Search elements in diagrams) clearly identifies the operation and resource, distinguishing it from create/update/export tools. However, it does not convey the extensive filtering and search options available, so it is clear but not fully descriptive.

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?

No usage guidance is provided. The description doesn't state when to use this tool versus alternatives like get_diagram_info or batch_operations, nor any prerequisites or context.

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