kingdee_query_bills

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

Annotations already mark it as read-only, non-destructive, and idempotent. The description adds that it supports filtering, sorting, pagination, and returns JSON with specified fields. It does not disclose additional behaviors like error handling or authentication 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?

The description is concise with two main parts: a summary of capabilities and examples. It is front-loaded with the primary purpose. Minor improvement could be more explicit structure, but overall 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?

Given rich annotations and a clear output schema (returns JSON with form_id/count/has_more/data), the description covers the key aspects. It lacks edge case details but is sufficient for a generic query tool with good structured data.

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?

Although the context signal claims 0% schema description coverage, the actual input schema provides descriptions for each parameter (e.g., form_id, filter_string). The description does not add substantial meaning beyond these schema descriptions, so baseline 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 clearly states it queries any Kingdee document list with filtering, sorting, and pagination. Examples of form_id are given. However, it does not explicitly differentiate from sibling specific query tools (e.g., kingdee_query_sale_orders), so distinguishing is implied but not explicit.

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 the more specific query tools. No when-not-to-use or alternative recommendations are provided. Only examples are given, which weakly imply usage.

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