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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered; the description adds that this is a write to an external provider via a specific HTTP route (GET /Orders/Get/{provider}/{store}/{id}) and that the identifier must be an exact match, which warns about lookup failures. It does not describe behavior when the order or store is not found.

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 a single dense but well-ordered sentence: the resource first, then the contents, then the prerequisites, then the route. Nothing is redundant, though the parenthetical provider list and endpoint could be trimmed for tightness.

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 carries the return-value burden and does so by enumerating totals, tax, discount, shipping, statuses, line items, and customer. Missing only edge-case behavior (unknown provider/store or order not found).

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%, so the baseline is 3; the description goes beyond the schema by telling the agent how to obtain valid provider/store values (see the contact's ExternalProviders/Shop) and by clarifying that order_id is the store's own id, not a CRM id.

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 ('Get'), a specific resource (one synced e-commerce order), and its scope ('by the store's own order id'), plus what the payload contains. It is clearly distinguishable from count_orders and the contact/deal siblings.

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?

It gives the practical prerequisite for a successful call – provider and store name must match exactly how Revamp CRM stores them, with a pointer to ExternalProviders/Shop on a contact. It does not explicitly rule out alternatives such as count_orders, so it stays just short of a 5.

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