record_start_tool

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

No annotations are provided, so the description carries the full burden. It usefully discloses that the tool blocks until guest consent, which is a key behavioral trait. It omits other important behavior such as whether the start is idempotent, what happens after unblocking, or any host-only permission requirement.

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 with no filler. It front-loads the action and includes the most critical constraint, making every word earn its place.

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?

An output schema exists, so return values need not be described. The description covers the core action and key blocking behavior, but it leaves parameter semantics and usage routing unaddressed. It is adequate but has clear gaps for a tool with one undocumented required parameter.

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 schema has one required parameter, project_path, with 0% description coverage. The description never mentions this parameter or explains how it relates to the 'current record room', making it unclear whether project_path identifies the room or is redundant. The description fails to compensate for the missing schema documentation.

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 identifies a specific action ('Host Start'), a clear resource ('current record room'), and a notable behavioral constraint ('blocked until guests consent'). It distinguishes from sibling record_* tools by naming the start operation, but it does not explicitly contrast it with record_resume_tool or record_land_tool.

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 phrase 'blocked until guests consent' gives an implicit precondition, telling the agent that consent is required before this action can proceed. However, there is no explicit when-to-use/when-not-to-use guidance and no reference to alternative tools, so the usage context is only implied.

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