getOrderDetail

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

No annotations provided, so description carries full burden. Only states 'Get detailed information' without specifying what 'detail' entails, such as included fields or data freshness. No mention of rate limits, authentication, or side effects.

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?

Single sentence, no redundancy, front-loaded with purpose. However, could include more substance without losing conciseness, such as listing key returned fields.

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?

Simple tool with no output schema, so description should hint at response structure. It does not mention what 'detailed information' includes (e.g., status, amount, timestamps). Lacks completeness for an agent to anticipate return value.

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?

Only one parameter (orderId) with 0% schema coverage. Description implies it identifies the specific order but adds no format or constraints beyond the schema. Adequate but minimal value over basic schema.

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?

Clearly states it retrieves detailed information for a specific P2P order. Verb 'Get' and resource 'detailed information of a specific P2P order' are well-defined. Distinct from list-based sibling tools like getOrderList or getAllOrders.

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?

Implies usage for obtaining details on a single order via orderId, but no explicit guidance on when to choose this over similar tools (e.g., getOrderList, getOrderHistory). No context about prerequisites or alternatives.

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