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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered externally. The description adds nothing beyond that — no mention of pagination, date-range semantics, or what the PO list contains.

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?

Two words is not conciseness but under-specification; there is no front-loaded statement of purpose to build on. Nothing is wasted, but nothing is delivered either.

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?

A read-only listing tool with four parameters, no output schema, and three near-identical siblings requires far more than a title fragment to be called correctly. Only the annotations save it from being entirely uninformative.

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 only 25% (only account_id is documented, and in Italian). The description does not compensate at all — days_back, po_item_state, and include_details are left completely uninterpretable, including the meaning of the state filter and the units/behavior of days_back.

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?

"Vendor POs" merely restates the tool name and the annotation title "Vendor purchase orders" — it names a resource but supplies no verb and no scope. An agent cannot tell what the tool actually returns or how it differs from siblings such as get_vendor_po_summary or get_vendor_purchase_order_details.

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 offers no when-to-use, when-not-to-use, or alternative guidance. With three closely related vendor PO tools in the sibling list, this absence is a real routing hazard.

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