build_xreal_apk

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

Describes async dispatch via EditorApplication.delayCall to avoid timeout. Annotations indicate non-readOnly and open world (side effects), which align with starting a build. No contradictions, and description adds useful context beyond annotations.

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?

Three sentences efficiently convey purpose, rationale for async, and next steps. No redundant information. Excellent structure for agent consumption.

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?

Covers main workflow: request returns jobId, then poll. With 12 parameters and no output schema, additional details like error handling or prerequisites would improve completeness, but core behavior is well explained.

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 covers 100% of parameters with descriptions, so baseline is 3. Description does not add parameter-specific meaning beyond what schema provides, but that is acceptable given high coverage.

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 queues an asynchronous Android APK build for XREAL One Pro and returns a jobId immediately. Distinguishes from sibling 'get_build_status' by mentioning polling. The verb 'build' and resource 'APK for XREAL One Pro' are specific.

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?

Explains why async is needed (Unity blocks) and instructs to poll 'get_build_status' with jobId. Does not explicitly mention when not to use or alternatives like 'build_pipeline', but the guidance is clear and actionable.

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