Build and deploy fresh robot code

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

With no annotations provided, the description fully informs about the tool's behavior: conditional build-then-deploy and app restart. It is transparent about the conditional sequence, though it could additionally explain what happens on build failure or side effects like potential disconnection.

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 two sentences, directly addressing the purpose and key behavior without any unnecessary words. It is front-loaded with the 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?

The description covers the main workflow but omits the return value or output format. Given the tool's moderate complexity and no output schema, mentioning whether it returns success/failure or logs would improve completeness. However, the provided details are largely sufficient.

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?

All 5 parameters are fully described in the input schema (100% coverage). The tool description does not add extra parameter meaning, which is acceptable given schema completeness. The schema descriptions are clear and sufficient.

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's purpose: it builds TeamCode first, conditionally installs the APK only on success, and restarts the Robot Controller app. This distinguishes it from sibling tools like 'build' (build only) and 'deploy' (deploy only) by emphasizing the safe competition-day deployment sequence.

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 explicitly recommends this as the 'safest competition-day deployment path', implying optimal use during high-stakes events. It does not explicitly state when not to use (e.g., for quick iterative testing) or contrast with sibling tools in detail, but the context is clear enough for decision-making.

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