design_annotate_pose

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

Since no annotations are provided, the description must carry the full burden of behavioral disclosure. It does not mention critical behavioral aspects such as required permissions, rate limits, or how the state of the skeleton layer is modified or preserved after the call.

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, highly effective sentence that packs the resource, the action, and the valid output scope into a concise format.

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?

The description is structurally complete for a simple annotation action, defining exactly what it does. However, in the absence of annotations, it lacks behavioral completeness, leaving gaps regarding the constraints and overall impact on the pose layer.

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 description coverage is 100%, meaning the parameter details are fully documented structurally. The description merely restates the types of annotations available, providing context for the enum but not semantics beyond the 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?

The tool's purpose is crystal clear: adding specific study annotations (landmarks, angles, distances, action lines) to a designated pose skeleton. It explicitly links the action to the resource (pose skeleton).

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?

While the description lists all valid annotation types, it does not provide explicit guidance on when to choose one type of annotation over another, nor does it differentiate usage from similar tools in the massive sibling list.

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