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

Annotations already declare destructiveHint=true, idempotentHint=false, readOnlyHint=false, so the mutation profile is known. The description adds useful semantics (null target unassigns; linked-file movement is explicit) but never says what is destroyed or overwritten — e.g. whether an existing project membership is replaced — which matters for a destructive tool.

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, front-loaded with the action, no filler. The final clause 'Linked file movement is explicit' is terse to the point of being cryptic, slightly weakening an otherwise tight statement.

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, non-idempotent mutation with no output schema and no per-parameter schema docs, the description covers the assign/unassign contract but omits permission requirements, whether existing assignments are overwritten, and batch-size/limit expectations (500 ids, 6 resource groups). Adequate but with clear gaps.

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?

With 0% schema description coverage the description must carry the parameter burden. It explains target_project_id's null behavior well, and the four resource types it names match the type enum, but 'Linked file movement is explicit' leaves move_linked_files ambiguous (default value? required flag?) and the resources array structure is not described.

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 ('Move ... into a project') and enumerates the exact resource types (jobs, files, workflows, workflow runs), so the agent can distinguish it from create_project, list_projects, and the per-resource mutation tools in the sibling list. The unassign clause further pins down scope.

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 explicit conditions for the assign and unassign directions ('Set target_project_id to null to unassign') and flags that linked-file movement is treated specially. It does not name an alternative tool, but no sibling is a plausible substitute for project assignment.

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