cortex_set_active_project

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

Description mentions loading a different .cortex DB and the blocking condition, but no annotations exist. It does not detail side effects like state resets, permissions required, or confirmation steps. Adequate but not comprehensive.

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 short, clear sentences. Every word is meaningful. The key information is front-loaded: purpose in first sentence, constraint in second.

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 simple action with one parameter and no output schema, the description covers the main functionality and a key constraint. Could mention what happens after success (e.g., return status), but not essential.

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?

The only parameter 'project_path' is described in the schema as 'Path to project directory'. The description does not add further semantic meaning beyond that, so baseline 3 is appropriate for 100% schema coverage.

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?

Clearly states the tool switches the active project by loading a different .cortex DB. The verb 'Switch' and resource 'active project' are specific, and the description distinguishes this from other cortex tools by focusing on project context switching.

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 notes when the tool is blocked (process started with --project), providing a clear when-not-to-use condition. However, no explicit alternatives are given among the siblings, but the constraint is helpful.

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