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

Annotations mark readOnlyHint=false and destructiveHint=false, so the description's key addition is that it returns a proposal without applying suggested changes, resolving the ambiguity of a non-readOnly hint. It also discloses latency (may take several minutes) and progress notifications, though it says nothing about auth needs or rate limits.

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?

Four short sentences with the purpose front-loaded and no filler. The save-workflow and latency notes are each worth their space, though the middle two sentences could be tightened into one.

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?

Output schema exists, so return values need not be restated, and annotations carry the safety profile. The description covers the propose-then-commit workflow and runtime cost, leaving only minor gaps such as what the proposal contains.

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 project_id and user_message are already documented in the schema. The only parameter-like names in the description (assessment_score, assessment_details) belong to projects_patch, not this tool, so the description adds no parameter meaning of its own.

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 and object: assess project description and story completeness. It is clearly distinguishable from CRUD siblings, though it doesn't explicitly contrast itself with the similarly-aimed projects_analyze or projects_check_description, so the boundary is left for the agent to infer.

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 a concrete workflow: this tool only proposes, then the agent must review with the user and persist accepted changes via projects_patch (with assessment_score/assessment_details) or the existing CRUD tools. It names the follow-up tool explicitly, but offers no when-not-to-use guidance versus the other analysis siblings.

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