Push project

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

Annotations only give the safety profile (readOnlyHint=false, openWorldHint=true, destructiveHint=false); the description adds substantial behavior beyond them: atomicity, execution from a sealed private admin repository, use of the authorized direct destination, read-back of every remote ref before success, and the specific failure modes that refuse publication. It also discloses the GitHub push-protection error path, which is exactly the kind of operational detail an agent needs.

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?

Front-loaded with the action and its atomic semantics, followed by environment and refusal conditions. No filler sentences. The failure-mode list is long but each item is a distinct refusal condition that earns its place, so it stays efficient.

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?

Failure behavior, atomicity, and verification are covered well, which matters most for a publish operation. But with no output schema and an undescribed 'path' parameter, the definition still leaves open what the argument identifies, what a success result looks like, and whether any dry-run or targeting option exists.

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?

The single parameter 'path' has 0% schema description coverage, and the description never mentions it or explains what it points at (checkout root? project directory?). With one undocumented parameter the description is the only place this could be clarified and it is not, so it fails to compensate for the coverage 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 scope: atomically publishing a clean checkout's exact current branch and release tag. That is far more precise than the title 'Push project'. However it never distinguishes itself from the many sibling push tools (repository_manager_push_projects, repository_manager_phased_push, rm_git_push, repository_manager_validate_and_release), so an agent must still infer the difference from the name.

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 refusal list (dirty state, gate failure, identity/config drift, non-fast-forward, tag collisions) implicitly tells the agent this should only be invoked on a clean, gate-passing checkout, which is useful invocation context. But there is no explicit when-to-use statement and no routing to alternatives such as the plural push_projects or phased_push, so the guidance remains implied.

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