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

Annotations only declare the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=true), so the description earns credit for disclosing latency ('may take several minutes') and progress-notification behavior. It does not state what the feedback contains or that the check is nondeterministic/LLM-backed, which openWorldHint implies but the text never confirms.

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 purpose, then the non-mutation guarantee, then the latency caveat. No wasted words, though 'Returns feedback' is slightly vague given an output schema exists.

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?

With an output schema present, return details need not be spelled out, and the description covers the two things an agent most needs: that this is a pass/fail gate rather than a mutation, and that it can run for minutes with progress notifications. It omits any criteria for what 'sufficiently detailed' means, which would help the agent interpret results.

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 title, llm_name, and description are already documented in the schema. The description adds only that the 'description' text is the thing being evaluated, and says nothing about why title/llm_name are supplied to a check operation, leaving the baseline 3 appropriate.

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 target ('Check whether description text is sufficiently detailed') and immediately scopes it against the sibling it could be confused with ('does not create a project'). An agent can separate it from projects_create and projects_make_description without opening schemas, though the description never names those siblings directly.

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?

The trigger point is explicit: run this 'before creating a project' as a validation gate. It also clarifies the negative case (it returns feedback, it does not create), but gives no guidance on what to do when the check fails or on alternatives for generating/fixing a weak description.

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