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

The annotations already establish read-only, idempotent, non-destructive, and open-world behavior. The description adds useful scope and safety context with 'owner-scoped' and the caveat that modeled sphere validation is not physical safety certification or permission to actuate, but it does not explain authorization requirements or receipt behavior in more detail.

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 definition is short and front-loads the core read operation. The second sentence carries a safety caveat that may be relevant, though 'modeled sphere validation' is not elaborated and the sentence is less directly tied to invoking the tool.

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?

Because an output schema exists, the description does not need to explain return values. However, for a read tool with a required job_id, it should do more to clarify how this receipt differs from result, status, and artifact siblings and how the job identifier is obtained.

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?

The schema has 0% description coverage for its single required job_id parameter, and the description does not mention job_id or explain its format, source, or scope. The parameter name is somewhat self-explanatory, but the description does not compensate for the schema's missing semantic detail.

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 gives a specific verb and resource: 'Read owner-scoped motion receipt.' It is clear what the tool returns at a high level, though it does not explicitly distinguish this receipt from sibling artifacts such as get_cloud_motion_result or get_cloud_motion_status.

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 explicit guidance on when to use this receipt tool versus get_cloud_motion_result, get_cloud_motion_status, or get_cloud_motion_artifact. The owner-scoped wording gives context but does not provide alternatives, exclusions, or prerequisites.

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