ads_dashbord_start

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

With no annotations, the description carries the full behavioral burden. It usefully discloses local storage of sensitive OAuth data and that it never performs billing or campaign actions, but it omits lifecycle details such as whether the server blocks, what it returns, or what happens if restart is false and a page is already running.

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 purpose is front-loaded in the first sentence, and the restart guidance is a separate concise sentence. The long list of stored credential types adds useful security context, though it makes the first sentence dense.

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 no annotations, no output schema, and 0% parameter coverage, the description covers purpose, local credential storage, and safety boundaries reasonably well. It is still missing port semantics, return behavior, and process lifecycle details that an agent needs to invoke it confidently.

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 explains the meaning of restart=true well but says nothing about the port parameter, leaving one of the two parameters undocumented in both schema and description.

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 gives a specific verb and resource: 'Start the local AdsMCP settings page on 127.0.0.1.' It implicitly distinguishes itself from campaign/billing siblings by stating it 'never performs billing or campaign actions,' though it does not explicitly differentiate itself from ads_dashbord_stop.

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?

It gives one clear conditional: 'Use restart=true only to replace an already-running page.' However, it does not explicitly say when to use this tool versus ads_dashbord_stop or other setup/auth tools, leaving the broader usage context implied.

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