get_pose

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

With no annotations, the description carries the behavioral disclosure burden. It clearly states this is a read operation, that it returns current data, that the data is local, and that both degrees and quaternions are involved. It does not discuss return structure, but the presence of an output schema helps cover that.

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, information-dense sentence with no filler. The action, scope, frame of reference, and units are all front-loaded, making it immediately scannable for an agent deciding whether to invoke 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?

For a parameterless read tool with an output schema available, the description covers the essential operational details. It could be slightly more explicit about whether the returned data includes both degrees and quaternions simultaneously, but the output schema likely resolves that; overall the definition is sufficiently complete for correct invocation.

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 tool has zero parameters, and the schema confirms this, so there is nothing for the description to elaborate on parameter semantics. The baseline for a zero-parameter tool is 4, and the description appropriately focuses on the operation and output rather than adding nonexistent parameter details.

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 a specific verb ('Read') and a clear resource ('all current local Pose Bone rotations'), and it specifies units ('degrees and quaternions'). This cleanly distinguishes it from write-oriented siblings like set_bone_pose and set_pose_batch, and from get_rig, which likely targets rig structure rather than pose rotations.

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?

The description implies when to use the tool: whenever you need the complete current local pose rotation data. However, it gives no explicit guidance about when not to use it or which sibling alternative might be better for a more specific need, such as reading a single bone or retrieving rig-level transforms.

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