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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is fully covered. The description adds only the scoping fact that a single record is fetched by ID; it says nothing about missing-ID behavior (e.g., error vs null) or any auth requirement. With annotations carrying the load, this is a baseline 3.

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 short sentence with the resource and the ID-based scope front-loaded; no filler. It is efficient, though there is no additional structure (no notes on errors or return shape) to earn a 5.

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-parameter read-only getter whose annotations cover the safety profile, this is minimally sufficient. However it omits anything about the returned object or not-found handling, and with no output schema the description could reasonably say more to fully orient the agent.

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% and the sole parameter (id, a UUID) is fully documented in the schema, so the description adds no syntax or format detail beyond it. Baseline 3 applies when the schema does the heavy lifting.

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 ("Get"), resource ("project system class assignment"), and scope ("single...by ID"), which distinguishes it from the sibling list/get variants like list_project_system_classes and get_project_system. The phrase "by ID" clarifies it is a point lookup rather than a search. It is clear but does not explicitly name which sibling it is not.

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?

Usage is only implied: "single...by ID" signals this is for retrieving one known record rather than listing. There is no explicit statement of when to prefer this over list_project_system_classes or get_project_system, nor any prerequisite or fallback guidance. Adequate but not routing-grade.

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