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

Adds real behavioral context beyond the annotations: each call appends a commit rather than replacing history, and the first invocation requires a repository target. It does not cover auth/permission requirements, though destructiveHint=true and openWorldHint=true already flag the safety and external-impact profile.

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 sentences, front-loaded with the usage trigger, then behavior, then parameter guidance. No filler or repetition of the schema.

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?

An output schema exists so return values need no explanation. The description covers the trigger, commit semantics, the alternative tool, and the one-time setup path, which is everything an agent needs to invoke it correctly.

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?

At 67% schema coverage the description earns its keep by explaining that repo must come from get-github-status, that create_repo makes a new private repository, and that they are alternatives passed on the first call. The required site_id is left to 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?

States a specific verb and resource: 'Commits and pushes the saved site to its repository'. It clearly distinguishes itself from pull-from-github and get-github-status by naming its direction and by routing other git operations to edit-site.

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 an explicit trigger ('when the user wants their WebTwizz site's code on GitHub'), names the alternative for other git work ('undoing a push, goes to edit-site'), and spells out the first-call branch condition for repo vs create_repo.

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