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

Annotations already flag non-read-only, destructive and open-world; the description adds real value on top by disclosing that each call appends another commit (cumulative history, not a reset) and that repo must come from get-github-status. It does not explain what makes the operation 'destructive' or what happens on conflict/failure, leaving a small gap against the annotation bar.

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 tight sentences, front-loaded with the trigger, then the behavior, then the exclusion, then the parameter setup. Every sentence carries distinct information with no restatement of the name or title.

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 the description needn't explain return values, and annotations cover the safety profile; the description supplies the commit-accumulation and first-run setup context an agent actually needs. It is nearly complete, missing only failure/conflict behavior and what site_id selects.

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 67%, so repo and create_repo are already documented; the description adds the crucial framing that they are alternatives used on the first push and that repo originates from get-github-status. site_id is left unexplained in both schema and description, which is the remaining gap.

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 — 'Commits and pushes the saved site to its repository' — and immediately distinguishes itself from sibling git work routed to edit-site. An agent can tell exactly what this does versus pull-from-github or get-github-status without opening the schema.

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?

Explicit trigger ('Use this when the user wants their WebTwizz site's code on GitHub'), explicit exclusion ('Other git work, like undoing a push, goes to edit-site'), and first-time setup guidance ('pass repo ... or create_repo'). Both the when and the when-not are named.

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