Connect a local project

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

Annotations indicate readOnlyHint=false and destructiveHint=false, but the description adds the key behavioral detail that non-Git projects have commit and push automatically disabled. This is useful context beyond the annotations and helps the agent anticipate side effects. However, it does not detail permission requirements or what happens to existing connections.

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?

Two concise sentences that immediately capture the primary purpose and a critical behavioral condition. No redundant phrases or filler; every clause earns its place.

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 tool with 5 parameters and no output schema, the description covers the main purpose and a key behavioral nuance but misses parameter semantics and clear usage steps. It does hint at the workflow (authorize before editing), but does not fully prepare the agent for correct invocation.

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 20% (just allowCommit). The description does not explain any of the parameters such as projectPath, label, writable, or projectId. With such low coverage, the description should compensate by describing parameter meanings, but it does not. The only implied hint is that allowCommit relates to the commit/push behavior, but it's not explicit.

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 clearly states a specific action (authorize a directory) and resource (one directory beneath a locally approved discovery root), and distinguishes it from siblings like disconnect_project and list_projects. The verb 'authorize' is precise and the scope is defined.

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 description implies usage context (connecting a project before editing) but does not explicitly state when to use this tool versus alternatives such as discover_projects or list_projects. No exclusions or alternatives are mentioned, so it relies on inference.

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