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

Annotations already mark readOnlyHint=false, destructiveHint=false, idempotentHint=false, so the agent knows this is a mutating but non-destructive operation. The description adds the target audience (team manager or organization admin+), which is helpful authorization context beyond annotations. However, it doesn't disclose whether the operation is reversible or what happens to the source process (e.g., is it moved or copied?). With annotations present, the description provides some extra value but not deep behavioral details.

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?

Two sentences, zero waste. The first sentence states the purpose and the second provides usage differentiation. Every word earns its place. Good front-loading.

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?

Given 3 required parameters, no output schema, and moderate sibling complexity, the description covers the core action and differentiation well. It lacks any mention of return value (though no output schema exists) or error conditions (e.g., what if the process is already filed). But for a simple filing operation, this is mostly adequate.

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 67%: parentId and processId have descriptions, orgId does not. The description adds context about processId by explaining that Unsorted processes are listed by getClarityProcessLandscape, which the schema doesn't mention. This helps the agent understand where to find the processId. However, no additional info for orgId or parentId beyond the schema. The description compensates for the coverage gap partially.

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 'File an existing Clarity process into an area of the process landscape', using a specific verb ('File') and resource ('process into landscape area'). It distinguishes from the sibling tool 'proposeClarityLandscapeProcess' by explicitly contrasting the use case (existing vs. brand-new process).

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 provides explicit guidance on when to use this tool: for processes that already exist but sit in 'Unsorted'. It also names the alternative tool ('proposeClarityLandscapeProcess') and its specific purpose (creating a brand-new one), making the choice unambiguous.

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