Add project

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

Annotations supply the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=true), so the bar is lower. The description does add one genuinely useful behavioral detail beyond the annotations: the '-A' wildcard means ALL changes are staged, not a subset. It stops short of saying whether staging is reversible, what happens to the index afterward, or whether the project must already exist.

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?

A single efficient sentence that front-loads the action and tucks the scope constraint at the end. Nothing is wasted, though the parenthetical '(git add -A)' could be split so the staging scope reads more prominently.

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?

The tool is simple (1 optional param, no output schema, annotations present), so the core action and scope are adequately conveyed. Still missing is any explanation of the 'path' parameter or default behavior, which is the main thing an agent must get right 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?

There is one parameter ('path') with null default and 0% schema description coverage, so the description must compensate. 'For a single Git project' implies the path identifies the target, but it never says whether path is a filesystem path, a project name, or that omitting it defaults to the current directory. The single most important parameter is effectively undocumented.

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?

The description gives a specific verb and scope: 'Stage all changes (git add -A) for a single Git project.' This is unambiguous and usefully rescues the misleading name/title 'Add project,' which suggests project creation rather than staging. However, it does not differentiate from close siblings such as rm_git_add or explain why 'single project' versus repository_manager_add_projects.

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?

There is no explicit when-to-use or when-not-to-use guidance. The phrase 'for a single Git project' hints at a scope constraint relative to the plural sibling, but the agent is left to infer that alternatives like rm_git_add or repository_manager_add_projects exist and when to prefer them.

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