open_cognee_workspace

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

No annotations; description covers the action (open UI) and what it provides. Does not disclose any side effects or behaviors beyond opening, but none expected for a UI opener.

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 concise sentences, front-loaded with the core action. No wasted words.

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?

Fully adequate for a zero-parameter, no-output-schema tool. Describes purpose and what the UI offers.

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?

No parameters in schema (100% coverage), so no need for param info. Baseline of 4 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?

Clearly states it opens the Cognee workspace UI and lists specific resources (dataset management, file upload, etc.). Distinguishes from siblings focused on individual actions.

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 example intents like 'run the cognee UI' and 'show the cognee app', guiding when to use. No explicit exclusions, but context with siblings suggests this is for generic UI access.

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