clusters_start

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

Annotations show readOnlyHint=false, indicating a write operation. Description adds only 'start', which is consistent but lacks additional behavioral details such as idempotency, error conditions, or permission requirements.

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?

Extremely concise: one sentence of 4 words. No wasted information. Front-loaded with the core action. Appropriate for a simple single-parameter tool.

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?

Despite simple interface, description is too minimal. Lacks usage context, preconditions, and behavioral details. Agent may not know that cluster must be terminated before starting, or that this is a state change operation requiring specific permissions.

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 coverage is 100% with cluster_id described as 'Databricks cluster ID'. Description does not add extra meaning beyond schema. Baseline 3 is appropriate for high coverage with no additional parameter info.

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?

Description clearly states the verb 'start' and the resource 'terminated cluster'. It distinguishes from siblings like clusters_restart (restart running cluster), clusters_create, and clusters_terminate. The action is specific and unambiguous.

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?

No guidance on when to use this tool vs alternatives (e.g., clusters_restart, clusters_resize). No mention of prerequisites (cluster must be in terminated state) or when not to use. Agent must infer usage from name alone.

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