pipeline_validate_full

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

No annotations are provided, so the description must disclose behavioral traits. It states the tool generates a report (non-destructive), but it does not explicitly confirm it is read-only, mention prerequisites (e.g., active scene with armature), or describe error states. The output schema exists but is not referenced.

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 concise: a single sentence summarizing purpose, a bullet list of checks, and two parameter descriptions. No redundant information, and key facts are front-loaded.

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 presence of an output schema (which likely documents return values), the description covers the main purpose, checks, and parameters. However, it does not explain how this fits into the pipeline (e.g., prerequisites or post-validation steps), leaving minor gaps about its integration with siblings like pipeline_avatar_from_mesh.

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?

With 0% schema description coverage, the description adds essential meaning: it explains each parameter's role (mesh_name to select a mesh or all, target for PC/Quest default). This compensates for the schema's lack of descriptions, though it does not address potential edge cases or format constraints.

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 clearly states it produces a comprehensive go/no-go validation report for VRChat uploads, listing specific checks (mesh, armature, shape keys, etc.). This distinguishes it from siblings like mesh_quality_check or vrc_validate, which likely have narrower scopes.

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 this tool is used before uploading to VRChat, but it does not explicitly state when to use it over alternatives (e.g., vrc_validate). No when-not-to-use or alternative guidance is provided, requiring the agent to infer usage from the purpose.

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