stop_spark_application

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

No annotations are provided, so the description bears the full burden. It states termination and removal from engine history, which is helpful. However, it lacks details on irreversibility, permission requirements, or impact on running queries. For a tool with no annotations, it provides basic but not comprehensive behavior info.

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 concise with a single-line summary, followed by structured Args and Returns sections. Every sentence adds value with no wasted words.

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 is simple (stop a spark app), and the description covers purpose, parameters, and return format. It mentions removal from history, which is a key behavioral detail. Given the presence of an output schema, it is fairly complete, though it could mention prerequisites like the engine existing.

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 input schema has 0% description coverage, so the description must compensate. It does so by clearly explaining each parameter: engine_id as 'Spark engine identifier' and application_id as 'Application identifier to stop', adding semantic meaning beyond the property names.

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 explicitly states 'Stop and remove a Spark application,' which clearly identifies the verb and resource. It distinguishes itself from sibling tools like submit_spark_application, get_spark_application_status, and list_spark_applications.

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 clearly states the action (stop and remove) but does not explicitly mention when to use this tool versus alternatives or when not to use it. However, the purpose is clear, and the sibling list indicates this is the only tool for stopping a Spark application.

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