bind_project

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

With no annotations present, the description carries the full burden and does disclose useful behavior: no file indexing occurs, the folder must pre-exist, and the effect is scoped to the current MCP session. It says nothing about what happens if the folder is already bound, whether the binding persists beyond the session, or what errors occur on an invalid project_id.

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 short sentences, front-loaded with the action, then preconditions, then identifier rules. Every sentence adds a constraint an agent would otherwise have to guess.

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?

An output schema exists, so return values need no explanation, and the identifier rule is well covered. However, for a mutation-style binding tool with zero annotations, the description omits the directory path's meaning and the behavior on duplicate or failed binds.

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 0%, so the description must compensate and it partially does: project_id is explained as requiring the exact value from list_projects, never a label. The path parameter is never mentioned directly, and its default of '.' is left unexplained, leaving a real gap for a 2-parameter tool.

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 ('Bind a folder to an existing project') plus the scope ('in this MCP session'), which is clear enough to act on. It does not explicitly distinguish itself from siblings like select_project or unbind_project, so an agent must infer the difference from names alone.

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?

Provides concrete preconditions: the folder must already exist, and this operation does not index files, which implicitly routes indexing work elsewhere. It also directs the agent to list_projects for the identifier and warns that labels are never identifiers. No explicit when-not or positive sibling comparison is given.

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