mp_setDefaultProject

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

Discloses that it does not establish a connection on its own, only sets the default, and that invalid or non-existent paths return errors. With no annotations provided, the description fully covers behavioral traits.

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?

The description is well-structured into logical segments (purpose, usage, parameter details, distinction) but is slightly verbose. It effectively front-loads the core message.

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?

Given no output schema and no annotations, the description provides comprehensive context: behavior, parameter usage, error handling, and relationship to sibling tools. No gaps remain.

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?

Despite 0% schema description coverage, the description adds critical meaning: projectPath is an absolute directory path from mp_listProjects projects[].path, and invalid values result in errors. This compensates fully for the lack of schema parameter descriptions.

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 the tool sets a persistent default project, using specific verbs ('set' and 'default project'), and distinguishes it from sibling mp_ensureConnection by emphasizing it only writes the default without establishing a connection.

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?

Explicitly indicates when to use: when only modifying the default project for future connections and not establishing a connection now. Contrasts with mp_ensureConnection's projectSelection and specifies that projectPath should come from mp_listProjects' output.

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