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

No annotation contradiction: the description says a mutating action while annotations set readOnlyHint=false. It adds useful scope (bulk, only visible, only unfiled, destination is suggested folder) beyond the annotations, but doesn't disclose possible partial failures, reversibility, or the effect on already-filed processes.

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?

A single front-loaded sentence that states the action, scope, and destination with no filler. Every phrase earns its place.

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 one-optional-parameter tool with no output schema, the description gives enough to invoke correctly. It could add a note about mass execution or confirmation behavior, but nothing critical is missing for selection and invocation.

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 only parameter, team_id, is fully described in the schema including fallback and OAuth behavior. With 100% schema description coverage, the description doesn't need to add parameter details; baseline 3 is appropriate.

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 names a specific verb ('File'), a bounded resource ('every unfiled process the viewer can see'), and the destination ('its suggested folder'). This clearly distinguishes it from per-suggestion accept/dismiss tools and manual move operations.

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 phrase 'every unfiled process the viewer can see' gives an implicit trigger condition for using this bulk filing tool, but it does not explicitly contrast with alternatives like acceptClarityCaptureSuggestion, dismissClarityCaptureSuggestion, or moveClarityProcessesToFolder. An agent has to infer when to choose this over those siblings.

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