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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds the useful detail that reserved quantity is included alongside on-hand stock, but says nothing about paginating through large result sets beyond what the schema's current_item already implies.

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?

Three short fragments, front-loaded with the returned data, then filter options, then endpoint. No filler, though the telegraphic style leaves out connective context that could aid an agent.

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?

With no output schema, the description does name the key returned fields, but it does not state default scope (all branches when branch_ids is omitted) or pagination expectations. Adequate for a read-only list tool with fully documented parameters, but leaves avoidable gaps.

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 100%, so every parameter is already documented with defaults, ranges and cross-references (e.g. branch_ids points to kiotviet_list_branches). The description only echoes the branch and last-change filters, adding no syntax or behavioral detail beyond the schema.

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 states a specific resource and payload: stock-on-hand and reserved quantity per product and branch, plus the underlying endpoint. It implicitly separates this inventory tool from catalog tools like kiotviet_list_products, but never names a sibling explicitly.

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?

It hints at two usage modes (filter by branch, filter by last change) which implies when the tool is useful, but gives no explicit when-to-use/when-not-to-use guidance or alternatives among the ~30 sibling tools.

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