get_camera_calibration

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

Since no annotations are provided, the description carries the burden of behavioral disclosure. It does state that the operation is a read, indicating non-destructive intent, and lists the categories of data returned. However, it does not mention error behavior, path dependency, coordinate frames, or any side effects, leaving some behavioral uncertainty.

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 a single front-loaded sentence with no filler words. 'Read' immediately conveys the operation, and the list of returned data is efficient and well-structured.

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 read operation with an output schema present, the description covers the main purpose and returned data categories. Still, the lack of parameter explanation and usage context means the description is only minimally complete for selecting and invoking the tool confidently.

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 description coverage is 0%, and the description does not compensate for that gap. It explains what is returned but not the meaning or usage of prim_path, command_id, or idempotency_key, so an agent must rely on property names and defaults alone.

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 uses the specific verb 'Read' and clearly identifies the resource as camera calibration, enumerating the data returned (intrinsics, extrinsics, projection, resolution, units). It is clear and unambiguous, though it does not explicitly differentiate itself from sibling read tools like get_prim_info or get_typed_attribute.

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?

No guidance is provided about when to prefer this tool over alternatives, nor are prerequisites or exclusions mentioned. The usage context is only implied by the word 'Read' and the tool's name; the description does not help an agent choose between this and related inspection tools.

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