start_local_meeting

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

With no annotations, the description carries the burden of behavioral disclosure. It adds meaningful traits beyond the schema: it is local, uses a Pro/Max subscription, and returns a meeting ID for follow-up messages. It does not mention persistence or cleanup, but key behavior is disclosed.

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 sentences, front-loaded with the primary action, and every sentence contributes a distinct piece of information: what, cost model, return value, and ideal use case.

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?

For a start-operation with 3 parameters and no output schema, it covers the purpose, the return value, and the key cost/selection context. Slight gaps remain around prerequisites (CLI must be installed/authenticated) and the lifecycle of the meeting, but the core call is well specified.

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 100%, so the baseline applies. The description adds no param-specific semantics beyond confirming the agenda is the discussion topic.

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 opens with a specific verb-resource pair: 'Start a LOCAL meeting with an agent using the installed Claude CLI.' It clearly distinguishes this from the sibling start_meeting by emphasizing 'LOCAL' and by explaining the billing model.

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 a concrete selection criterion: use this for cost-conscious, lengthy conversations because it uses Pro/Max instead of API credits. It does not explicitly name alternatives or exclusion cases, but the local-vs-API distinction provides clear context.

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