Start application

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

With no annotations, the description carries the full burden. It discloses the 'force rebuild' option, but it does not mention side effects, permission requirements, idempotency, or behavior if the application is already running. This is a minimal disclosure.

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 concise sentences that are front-loaded with the primary action. Every word serves a purpose, with no redundancy or filler.

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 tool has three parameters with no schema descriptions and no annotations, and the description omits 'instant_deploy' entirely. It also does not address return values or side effects, making it incomplete for an agent to understand the full behavior.

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?

The description clarifies 'uuid' as the application identifier and 'force' as triggering a rebuild, but it completely omits 'instant_deploy'. Since schema description coverage is 0%, the description only partially compensates for the three parameters.

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 action 'Start' and the resource 'application' with its identifier 'UUID', distinguishing it from siblings like 'stopApplication' and 'restartApplication'. The optional 'force rebuild' adds specific scope.

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 usage is implied by the verb 'start' and the mention of 'Optionally force rebuild', but there is no explicit guidance on when to use this tool versus alternatives like 'restartApplication' or 'deploy'. No exclusions or specific scenarios are described.

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