ba_session_start

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

No annotations are provided, so the description carries full burden. It discloses that readScope is persisted to the session and bounds ba_ground's auto-accept, providing some behavioral insight. However, it does not mention auth requirements, destructiveness, or side effects for other modes.

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 two sentences, concise, and front-loaded with the primary action. Every sentence adds value without extraneous information.

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 4 parameters, no output schema, and no annotations, the description lacks completeness. It does not explain return values, errors, session resumption, or the 'readDeny' parameter. For a central session management tool, more detail is needed.

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 coverage is 0%, so description must compensate. It explains 'mode' by listing enum values and explains 'readScope' for ground mode. However, 'readDeny' and 'projectRoot' are not described. 'projectRoot' is required but omitted, reducing clarity.

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 starts or resumes a BA session, lists the four modes, and distinguishes the ground mode's readScope usage. This differentiates it from sibling tools like ba_ground, ba_init, etc., which are likely actions within a session.

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 gives specific guidance for ground mode (pass readScope) but does not explicitly explain when to use this tool vs siblings, or when to start vs resume. Usage context is implied but not clearly stated.

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