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

Annotations already declare readOnlyHint=false, openWorldHint=true and idempotentHint=false, so the agent knows this is a non-idempotent, world-touching action. The description adds only the target ('the tab's URL') and says nothing about whether the audit is async, how results are retrieved (get_audit / tab_history), or whether it consumes quota.

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?

A single front-loaded sentence with zero waste, which is structurally fine. However, at six words it is arguably under-specified rather than concise, so it lands at the minimum viable level.

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 non-idempotent action tool with two required parameters (one undocumented) and no output schema, the description should say more about what happens after the run and how to obtain results. It leaves the agent without enough context to invoke or follow up correctly.

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 only 50%: 'id' is documented but 'guest_token' has no description anywhere. The description mentions no parameters at all, so it does not compensate for the gap, particularly for the undocumented auth token.

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 states a specific verb ('re-audits') and a specific resource ('the tab's URL'), which is far more useful than the bare title 'Run tab'. It does not distinguish itself from siblings such as audit_url or audit_site, which likely perform similar audit actions on different targets, so it stops short of a 5.

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?

There is no guidance on when to use this tool versus audit_url, audit_site, or watch_tab, nor any mention of prerequisites such as whether the tab must already exist. The agent must infer usage entirely from the name.

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