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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds only the raw endpoint path, with no information about error behavior for bad/unknown GUIDs, whether the record is authoritative, or what fields come back.

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 terse sentences with no waste, but 'Read the selected record' is a low-information filler phrase and the endpoint path carries most of the meaning. It is concise without being informative.

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 single-param read with readOnlyHint and no output schema, the essentials are close to covered, but the description never states what an order record contains or what happens on a missing id. Adequate, with visible 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 coverage is 100% and the single 'id' parameter is already documented as a ServiceMonster record GUID from a preceding read. The description adds no syntax or sourcing detail beyond that, so baseline 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?

The verb 'Read' plus the endpoint path 'GET /v1/orders/{id}' implies it fetches a single order by id, and the singular form distinguishes it from list_orders only by inference. The phrase 'the selected record' is vague and never names the resource outright, so the agent relies on the tool name to confirm it operates on 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?

There is no statement of when to use this tool versus the many siblings, notably servicemonster_list_orders or servicemonster_list_account_orders. The single-id shape hints at fetching one known record, but that must be inferred rather than read.

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