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

With no annotations, the description carries the full burden of behavioral disclosure, yet it never states that this is a read-only fetch, what permissions ('Owner or office') actually gate access, or what happens when the PO is not found. It only hints at returned content, and even that is largely covered by the output schema.

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?

It is short and leads with the most useful content (what the PO record contains), but it is a sentence fragment rather than a clear statement, and the dangling 'Owner or office.' consumes space without conveying anything an agent can act on.

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?

An output schema exists, so return-value detail is partly excused, but for a fetch tool with zero annotations and zero schema description coverage the definition should still state read-only behavior, required access level, and error handling. The ambiguous 'Owner or office' leaves the permission model unresolved.

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 0% for the single required po_id (uuid) parameter, and the description does not compensate — it never mentions the identifier or its format. The parameter is self-evident from the name, which keeps this from being a 1, but no added meaning is provided.

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 fragment names the resource (a purchase order) and enumerates its contents — lines, received quantities in job cost, and the supplier's bill — which distinguishes it from po_list's multi-record listing. However, there is no verb stating the action (retrieve/fetch), and the trailing 'Owner or office.' is opaque and adds no clarifying scope. An agent must infer the operation from the tool name po_get.

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?

There is no statement of when to use this versus po_list, po_receive, po_recordBill, or po_update. The phrase 'Owner or office' might be intended as an audience/permission hint but is never explained, so it provides no actionable routing guidance.

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