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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the agent knows this is a mutating operation. The description adds 'Validate, render, and publish,' providing some process context but no details on side effects (e.g., overwriting existing content, what gets destroyed). This is adequate but not rich, thus a 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?

The description is a single, tightly worded sentence with no redundant words. It front-loads the key verbs ('Validate, render, and publish') and is appropriately sized for the tool's scope, earning a top score.

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?

As a publish tool with destructive potential, the description provides no information on return values, prerequisites, or effects on existing site content. The absence of an output schema further increases the need for description detail, which is not met. Minimally viable but with clear gaps in operational context.

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 0% in the description; it neither explains the parameters nor the content format. The description mentions 'template-based' but not what 'site', 'template', or 'content' should contain. Parameter names provide minimal clues, but the vagueness of 'content' (untyped object) leaves the agent under-informed. A score of 2 reflects the lack of compensating detail.

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?

The description uses a specific verb ('publish') and resource ('template-based TON Site'), clearly stating the action. It distinguishes itself from sibling 'sites.publish_files' by explicitly mentioning template-based publishing, making the tool's purpose unambiguous.

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 is given on when to use this tool over alternatives like publish_files. The description merely states what it does, leaving the agent to infer usage from the name and sibling list without explicit criteria or exclusions.

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