bdesign_project_target

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

Annotations already declare readOnlyHint and idempotentHint. The description adds context about the session-binding side effect and the return of a workspace handoff, which are not covered by annotations. No contradiction between the description and annotations; 'bind' is a client-side state change, not a server data mutation.

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 that efficiently conveys the core purpose and return. It is front-loaded with the main action and avoids unnecessary detail, making it concise and well-structured.

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?

With four parameters, zero schema descriptions, and no output schema, the description should explain parameter roles and the return format. It only covers the session-binding purpose and a vague 'workspace handoff'. It lacks details on time, view, focusCardId, and what exactly the handoff contains, leaving the agent under-informed.

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 0%, so the description must compensate. It only mentions projectId implicitly through the binding purpose, but fails to describe time, view, or focusCardId at all. The phrase 'requested workspace handoff' hints at view but is not explicit. The description provides no semantic meaning for the majority of parameters.

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's purpose: binding the MCP session to a BeatDesign project so later project-scoped tools can omit projectId. It also mentions returning a workspace handoff. This is a specific verb+resource and distinguishes it from siblings like project_open or project_get.

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?

The description implies when to use it: before other project-scoped tools that rely on the bound session. It explicitly mentions the benefit (later tools may omit projectId) and the return value. However, it doesn't state when not to use it or provide alternatives, but the usage context is fairly clear.

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