obtener_posicion_junta

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

No annotations, but the description clearly indicates a read operation without side effects. Units are specified, but potential error conditions or return format are not mentioned.

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?

Single concise sentence with no redundant text, effectively communicating the purpose and units.

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?

Provides unit information indicating return type, but lacks explicit output schema or detailed behavior. Sufficient for a simple getter but not exhaustive.

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 parameter 'junta' is not described in the schema or tool description beyond the name, leaving the expected format (e.g., joint name) implicit. Minimal guidance for the value.

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?

Clearly states it reads a joint's position and specifies units (radians for revolute, meters for prismatic), distinguishing it from sibling tools like orientation and object position.

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?

Implies usage for querying joint positions, but does not explicitly contrast with alternatives like obtaining orientation or setting position. The units and purpose make the context clear.

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