Submit Machine Flag

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds genuinely new context: the operation is irreversible, user confirmation is required, and the difficulty value must be solicited from the user. It does not describe error behavior or what a successful submission returns, which keeps it out of the top band.

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?

Three sentences, each carrying distinct information: the action, the difficulty constraint plus user-prompt rule, and the irreversibility warning. Nothing is repeated from the schema and the critical warning is not buried.

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?

For a 3-parameter mutation with full schema coverage and annotations covering the safety profile, nothing essential is missing. There is no output schema to explain, and the description closes the main behavioral gap (irreversibility and confirmation) on its own.

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%, so the baseline is 3, but the description adds real meaning: it explains the 10-100 step-10 difficulty scale with human labels and clarifies that the flag value itself determines whether a user or root flag is being submitted. That is more than the schema's bare 'difficulty rating 10-100' text conveys.

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?

States a specific verb and resource ('Submit a user or root flag for a machine') and notes that the flag type is inferred, which separates it from htb_challenge_submit. An agent can identify the operation and its target without opening the schema.

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?

Gives concrete operational guidance: ask the user for a difficulty if one wasn't provided, and confirm before submitting because submissions are irreversible. It stops short of naming an alternative tool (e.g. htb_challenge_submit for challenges), so it is clear context rather than full when/when-not routing.

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