alcove_project_add

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

No annotations are provided, so the description must fully convey behavioral traits. It only states 'create or update' but does not disclose what happens on creation vs update, whether it overwrites, side effects, authentication needs, or idempotency. This is insufficient for an AI agent to predict tool behavior.

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 very brief (one sentence), but it under-specifies the tool. Conciseness should not come at the expense of essential information. The single sentence does not earn its place as it adds little beyond the tool name.

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 the complexity (5 parameters, no schema descriptions, no annotations, but with an output schema), the description is extremely incomplete. It omits parameter definitions, usage examples, return value details, and any behavioral notes. The output schema is present but the description does not leverage it to explain what the tool returns.

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?

There are 5 parameters with 0% schema description coverage. The description adds no meaning to any parameter (e.g., what 'home', 'note', 'path', 'alias', 'workspace' represent or how they affect the operation). The agent cannot determine correct parameter usage from the description alone.

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 creates or updates a global project alias. This is specific and distinguishes it from sibling tools like alcove_project_find, alcove_project_list, etc. However, the term 'global project alias' could be defined more explicitly.

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 on when to use this tool over alternatives (e.g., other project tools). The description does not mention any prerequisites, typical use cases, or when to avoid using it.

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