get_build_status

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

Describes state transitions (Queued -> Building -> Succeeded | Failed), response fields per state, and the effect of omitting jobId. Annotations confirm read-only behavior; no contradiction.

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?

Very concise (3 sentences), front-loaded with main purpose. Every sentence adds value: purpose, how to use, and behavior variations.

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?

With only 1 parameter and no output schema, the description fully covers behavior, state machine, response fields, and edge cases. No gaps.

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 has 100% coverage (jobId described). Description adds that jobId comes from build_xreal_apk and that omitting it lists all jobs, plus response details per state.

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 the tool returns the status of an asynchronous build, linking it to build_xreal_apk via jobId. It distinguishes from siblings like build_xreal_apk by being the status checker.

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?

Explicitly tells when to use (after build_xreal_apk with jobId) and when not (omit jobId to list all jobs). Provides clear context for alternatives.

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