queryAbnormalDrawingList

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

Discloses internal API calls, fixed parameters (className, fileType), and that returned context includes record IDs. No annotations provided, so description carries burden; it offers good insight beyond basic functionality, though omits error handling and auth requirements.

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?

Concise and well-structured: front-loads main purpose, then explains internal steps. Could be slightly shorter, but remains efficient.

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?

Covers key aspects: pagination, internal process, fixed parameters, and returned context (ids). Lacks output schema, but description compensates with details. Sufficient for typical use.

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?

Adds meaning beyond schema: explains filters parameter semantics (field names, fuzzy/range matching), and that fileType is fixed. With 100% schema coverage, baseline is 3, but description enhances understanding.

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 clearly states the tool's purpose: paginated query of SOP abnormal drawing list. It details the internal process (two API calls) and fixed parameters, distinguishing it from sibling tools like auditProductionTask and querySopList.

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 explicit guidance on when to use this tool versus alternatives. While it describes what it does, it lacks conditions, exclusions, or references to sibling tools.

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