rig.pose_report

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

No annotations are provided, so the description must carry full behavioral disclosure. It states 'report' which implies a read operation, but does not specify what transforms are reported (local, world), whether constraints include all or only active, or any prerequisites like armature must be in pose mode.

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 sentence with no waste, but it could be expanded with key details without much verbosity. It achieves minimal conciseness but sacrifices informativeness.

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?

Given the lack of output schema and annotations, the description is too brief. It does not explain what the report returns (e.g., transform values, constraint list), leaving the agent uncertain about the tool's output. Sibling tools like rig.report might overlap, but no disambiguation is provided.

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%, meaning the description does not mention the two parameters (armature, bone). It adds no meaning beyond the titles in the input schema, leaving the agent unclear about how the optional bone parameter filters the report.

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 'Report pose bone transforms and constraints' uses a specific verb-reource combination. It clearly distinguishes from sibling tools like rig.list_bones (lists bones) and rig.report (generic report), as well as rig.set_pose_bone (modify).

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 on when to use this tool versus alternatives such as rig.report, rig.list_bones, or rig.constraints. The description lacks any when/when-not or context information.

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