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 nothing behavioral beyond the schema — no mention of not-found handling or scope of the returned record — so it earns little credit even against the lowered annotation-assisted bar.

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 no waste, appropriately sized for a one-parameter read tool. It is terse but not padded, though it borders on under-specification rather than tight completeness.

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 get-by-id tool whose annotations cover safety and whose single parameter is fully documented, the description is adequate to invoke it correctly. It is thin given there is no output schema and no note of what the returned phase contains or how errors surface.

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 coverage is 100% and the single `id` param is documented in the schema as a project phase UUID. The description's 'by ID' merely echoes the schema, adding no semantics such as ID source or format, so the baseline 3 applies.

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) plus resource (project phase) and adds scope ('single... by ID'), so the agent knows it retrieves one entity rather than a collection. It does not differentiate from the many get_*/list_* siblings (e.g., list_project_phases, get_project_milestone), which keeps it from a 5.

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?

No guidance on when to use this versus list_project_phases or other retrieval tools, and no preconditions. The only implicit cue is 'single... by ID', which is usage-adjacent but not stated as a selection rule.

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