Get change order

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

Annotations already declare read-only, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds useful behavioral context by enumerating what is returned: description, status, total, project, customer, date, reason, source estimate, time delay, and priced line items.

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 short and front-loaded, with the main purpose in the first sentence and return details in the second. There is minor repetition between 'One change order or request' and 'Everything on one change order or change order request', but the field enumeration earns its place.

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?

For a simple single-record retrieval tool with no output schema, the description provides enough detail about the returned fields and the annotations cover safety and idempotency. It does not mention not-found behavior, but that is a minor gap for this retrieval operation.

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?

There is only one parameter and the schema describes it fully as coming from list_change_orders, giving 100% schema coverage. The description adds no additional parameter semantics beyond what the schema already states, so the baseline of 3 is appropriate.

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 identifies the resource as a single change order/change order request and enumerates the data returned, distinguishing it from list_change_orders by emphasizing 'One'. It lacks an explicit action verb like 'retrieve', but the tool name and content make the purpose unambiguous.

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?

Usage is implied by 'One change order or request' and the schema note that the ID comes from list_change_orders, but the description itself gives no explicit when-to-use guidance or alternatives. An agent can infer this is for fetching a single record rather than listing or mutating.

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