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

Goes beyond the annotations by disclosing that live files are not modified, that a new branch is created with a default name pattern (server/<server>-<date>), and that a write-scoped deploy key is required. It does not say what happens if the branch already exists or how failures/approvals behave.

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 compact sentences, front-loaded with the core action, then the default naming, then the follow-up and prerequisite. Dense but every clause carries information; the first sentence is long but still readable.

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 non-idempotent open-world write tool with no output schema and 7 parameters, the description covers the key safety and workflow facts. Remaining gaps are the undocumented approval_id/message/server parameters and behavior on branch collisions.

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 description coverage is only 29%, but the description clarifies path vs paths ('only paths') and explains branch defaulting. It leaves why, message, server, and approval_id entirely unexplained in both description and 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 live folder changes and pushes them to a new GitHub branch. It also disambiguates the scope (all changes vs. only given paths) and distinguishes itself from the git_link prerequisite and the gh_pull_create follow-up.

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 explicit context for use (snapshot of live files without touching them) and names the next step, gh_pull_create. It also states the precondition (deploy key with write via git_link). It does not contrast with git_deploy or say when not to use this tool.

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