Push projects

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

Annotations declare the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=true), so the agent already knows this is a non-destructive network write. The description adds the genuinely useful 'in parallel' concurrency trait, but says nothing about auth requirements, partial-failure handling, or whether the operation is reversible.

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?

One short sentence with the concurrency trait front-loaded and zero filler. It is efficient, though its brevity is part of why other dimensions are thin.

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 mutating, open-world bulk tool with one undocumented parameter and no output schema, the description is inadequate: it omits failure semantics, scope defaults, and any result behavior, leaving the agent unable to predict what calling it will do.

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 project_dirs has 0% schema description coverage and the description does not mention it at all — it doesn't explain the expected directory format, whether it accepts globs, or what happens when it is omitted (default null). The description does not compensate for the schema 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 (push) and resource (projects), and the plural plus 'in parallel' implicitly distinguishes it from the singular repository_manager_push_project. However, it never clarifies the destination (git remote?) or what 'updates' means, so it stops short of a fully self-contained purpose.

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?

No when-to-use guidance at all. With siblings like repository_manager_push_project, repository_manager_phased_push, and rm_git_push, the description gives no condition for choosing this bulk variant over them, leaving the agent to infer that 'multiple projects' is the selector.

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