macro_start_recording

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

With no annotations provided, the description carries full burden but only states 'start recording'. It discloses no behavioral traits like what happens during recording, whether it requires user interaction, or what state changes occur. This is insufficient for safe invocation.

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 extremely concise at 4 words, but this conciseness sacrifices necessary information. It is not verbose, but it is under-specified for the task.

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 the tool's role in a macro recording workflow (siblings include stop, pause, run), the description lacks any mention of recording lifecycle, dependencies, or typical usage flow. No output schema exists, so description should clarify what happens after starting.

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 has 0% description coverage, and the tool description does not explain the parameters 'name' and 'description'. The description fails to add any meaning beyond the raw schema, so the agent does not know how to use these parameters correctly.

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 'Start recording a new macro' clearly identifies the action (starting recording) and the resource (a new macro). It distinguishes from sibling tools like 'macro_stop_recording' and 'run_macro', but lacks detail on macro type (native vs VBA) which exists among siblings.

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?

No guidance on when to use this tool versus alternatives such as 'create_initialized_macro' or 'start_native_macro_recording'. No prerequisites or conditions (e.g., must a model be open?) are mentioned.

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