kingdee_query_material_target_cost

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, so the safety profile is clear. The description adds that the tool returns a JSON-formatted list (effectively a string), and its example filters provide insight into common usage patterns. No behavioral contradictions.

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 and structured with a brief statement of purpose, followed by examples and return type. Every sentence adds value. It could be slightly more organized (e.g., separating purpose and examples), but overall it's 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 that an output schema exists (mentioned in context), the description does not need to detail return values. It covers purpose, parameters (via examples), and return format. It could mention pagination or error handling, but for a read-only query tool this is adequate.

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 includes descriptions for each parameter, providing baseline understanding. The description adds value by offering concrete filter_string examples (like 'FDocumentStatus='C'') and recommending specific field_keys, which goes beyond the schema's generic descriptions and clarifies practical usage.

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 verb '查询' (query) and the specific resource '物料目标成本单' (material target cost order), and mentions the form ID 'BD_MatTargetCost'. This distinguishes it from sibling tools like kingdee_query_material_cost, which deal with similar but different entities.

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 practical usage tips through filter string examples and recommended field keys, which helps the agent know how to use the tool effectively. However, it does not explicitly state when to use this tool versus other query tools (e.g., cost calculation vs. cost items), nor does it mention any prerequisites or exclusions.

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