wisdom_set_project

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states that the tool sets the current project context; it does not mention that this mutates the active project state, that persistence to a config file can be controlled, or what side effects future commands may see.

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 a single sentence with no wasted words and the core action is front-loaded. It is concise, though almost too terse to fully convey the tool's purpose and effects.

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 state-changing tool with no annotations and no output schema, the description is too thin. It does not explain that this changes the active project for subsequent operations, that persistence is configurable, or how it relates to the sibling get/clear project tools. A two-sentence description could easily make this complete.

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 100%, so the schema already documents the 'project' UUID and 'persist' flag. The description adds little beyond the schema, but because the schema is fully covered, the baseline of 3 is appropriate.

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 'Set the current project context' uses a clear verb ('set') and a specific resource ('current project context'), and it is distinct from the sibling wisdom_get_project and wisdom_clear_project. It is not a tautology, though it does not explicitly differentiate itself from those siblings.

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 guidance is given about when to use this tool versus alternatives like wisdom_clear_project or wisdom_get_project. The description implies a context-switching use case but provides no exclusions, prerequisites, or situational advice.

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