Render a Posecode movement to a link

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

Discloses that validation and link generation occur, but no annotations exist. Does not specify validation error behavior, authentication needs, rate limits, or the exact format of the returned link. Additional details would improve transparency.

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?

Two sentences, front-loaded with key action and outcome. No redundant words; every sentence carries essential information.

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 single parameter and lack of output schema, the description sufficiently covers what the tool does and what input is required. Minor gap: does not specify that the permalink is returned as a string in the response, but it's implied.

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 coverage is 100% with a clear description of the 'source' parameter. The description repeats 'full .posecode document text' without adding new semantics, so it meets the baseline but adds no extra 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 the tool validates a .posecode document and returns a permalink linking to an animated 3D figure in the playground. Distinguishes from sibling tools (posecode_authoring_guide and validate_posecode) by providing the rendered link.

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 use when a viewable, animated representation is desired, and that the input must be a .posecode document. However, lacks explicit guidance on when not to use this tool (e.g., when only validation is needed) or alternatives.

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