Add/update a website page

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

Annotations are all false, so the description carries the burden. It discloses the side effect 'Re-renders all pages so theme/gate stay consistent,' which is a key behavioral trait. However, it doesn't clarify if the operation is destructive or idempotent, but the 'update' implication and lack of destructive hint suggest non-destructive.

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 concise, using two sentences to convey purpose, output, and a notable side effect. It is front-loaded and free of unnecessary detail.

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 tool with 5 parameters and no output schema, the description lacks details about return values, error conditions, prerequisites (e.g., project existence), and conflict handling. The side effect is mentioned, but overall completeness is moderate.

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?

With schema description coverage at 40%, the description adds minimal value: it mentions 'title and sections' but does not clarify 'project' or 'seo' beyond what's in the schema. The baseline is 3 due to coverage, and the description does not significantly enhance understanding of parameters beyond the schema.

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 clearly states the tool adds or updates a sub-page of the project site, specifying the output path (site/<slug>.html) and distinguishing from set_site for the home page. It is specific and unique among sibling tools.

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 description explicitly says not to use for home page (managed by set_site), implying use cases for sub-pages. It could be improved by mentioning alternative tools like set_page_seo for SEO-only updates, but the current guidance is clear enough.

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