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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the mutation profile is covered. The description adds real value beyond that: engine-owned paths are rejected (a guarded constraint) and the deletion is recorded as a checkpoint plus chat note, which is non-obvious side-effect behavior an agent wouldn't infer from annotations.

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 short sentences, each earning its place, with the core action front-loaded before the path restriction and side-effect notes. No 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?

For a destructive 3-parameter mutation with no output schema, the description covers the action, a guard condition, and side effects, which is decent. However it omits reversibility/undo behavior, permission requirements, and any return/error detail beyond the engine-path rejection.

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 description coverage is 0%, so the description must carry parameter meaning. 'By path' and 'a flow's tree' give partial semantics for the paths array and imply flowId, but the 'agent' parameter is completely unexplained and no path syntax/format is given. Coverage of the three parameters remains thin.

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 (remove) plus resource (files in a flow's tree) and the scoping mechanism (by path). It clearly contrasts with the sibling read/write pair, flow_read_flow_files and flow_write_flow_files, since 'remove' names the delete operation distinctly.

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 establishes the delete context and notes that engine-owned paths are rejected, but it never explicitly says when to choose this over flow_write_flow_files or what prerequisites apply. Usage is implied by the verb rather than stated.

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