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

Annotations already declare read-only, non-destructive, idempotent behavior, so the safety profile is covered. The description adds little beyond that, though it does clarify that the resource is project-specific assignment data; it says nothing about pagination, auth, or return shape.

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, front-loaded and free of filler. The second sentence is somewhat redundant with the schema's filter descriptions, but the overall structure is efficient and easy to scan.

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 simple, read-only list tool with rich annotations and full schema coverage, the description covers the core purpose and filtering options. It does not explain return values or pagination, but the schema handles pagination and no output schema exists.

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 100%, so the schema already documents all four parameters. The description names the two filter parameters but adds no extra meaning or format detail beyond what is already in the schema.

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 states a specific verb and resource: list system class assignments for projects. It is clearer than a bare name, but it does not explicitly name or distinguish itself from sibling list tools like list_system_classes or list_project_systems.

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 implies usage by mentioning available filters, but gives no explicit when-to-use guidance, prerequisites, or alternatives to sibling tools. An agent must infer that this is the tool for project-scoped system class assignment lookups.

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