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

Annotations already declare a safe, closed-world read. The description adds genuinely new behavior: ownership is enforced server-side rather than by a caller-supplied filter, and archived work is silently omitted from results. That archived-exclusion detail matters because it explains why a known assignment may not appear.

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 ownership scope and the filter, and the closing clause about archived work is the only place it could be. No repetition of the title or annotations.

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 two-parameter list tool this covers scope and filtering adequately, but with no output schema the description never indicates what an assignment record contains or how results are ordered or paged. The undocumented limit parameter compounds the gap.

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 carries the full burden. It clarifies only the status filter ('optionally narrowed by status') and says nothing about the limit parameter, its maximum of 50, or its default, leaving half the inputs unexplained in both schema and prose.

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 resource (assignments), a specific owner scope (the CALLER), and the cross-project breadth, so an agent can distinguish it from general assignment-list tools. It stops short of naming any sibling explicitly, which is what a 5 would require.

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?

It gives clear calling context: use it when you want the caller's own work, optionally narrowed by status, and never for another person's list. It does not point to an alternative tool for the cases it forbids, so a stronger routing statement is missing.

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