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

Annotations already cover the safety profile (readOnlyHint, destructiveHint false, openWorldHint), so the bar is lower, yet the description adds real value: it discloses the return shape (per-connection status values success/error/run/queued, save_po flag, external id and reference). It also restates read-only, consistent with annotations.

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?

Front-loaded with the core purpose, followed by return-field detail and the endpoint. Dense but every clause earns its place; only slight redundancy in restating the read-only nature already implied by annotations.

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 compensates well by enumerating the returned status values and flags, which is exactly what an agent needs to interpret results. Missing only explicit guidance on when to prefer this over sibling retrieval tools.

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% with a single well-documented purchase_order_id, so the schema carries the semantics. The description adds nothing about the parameter beyond echoing the endpoint's {id} placeholder, so the baseline of 3 applies.

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?

States a specific verb and resource (get purchase order connections) and immediately clarifies what 'connections' means: whether/how the PO was saved to connected systems like ERP or accounting. This clearly distinguishes it from siblings such as get_purchase_order or list_purchase_orders.

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 implies the use case (checking sync status to connected systems) but never states when to use this versus get_purchase_order or get_purchase_order_stock_update. No explicit alternatives or exclusions are named, leaving routing to inference.

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