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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered structurally. The description adds genuine value by naming the fields each preset returns and by tying the output to a subsequent deploy_site call, telling the agent the results are meant as valid input arguments elsewhere.

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 short sentences with zero filler: the first delivers the resource and its contents, the second delivers the next action. Nothing is buried and nothing is redundant.

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 no parameters, an output schema present, and read-only annotations, the definition covers everything an agent needs to call and act on it. The only minor omission is any hint about framework-name matching (e.g., exact/case-sensitive values), which would prevent a failed deploy_site call.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The mention of a 'framework name' correctly signals that the returned values are meant to be passed as an argument to another tool, not passed in here.

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 resource ('List framework presets') and immediately enumerates what a preset contains (install command, build command, output directory), which disambiguates it from every other list_* sibling. The downstream link to deploy_site further pins down its role in the workflow.

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 clear context for use ('for building a site from source') and an explicit follow-on action ('Pass the framework name to deploy_site'), which effectively tells the agent when this tool matters. It stops short of stating exclusions or prerequisites, but there is no competing sibling that would require an explicit 'use X instead'.

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