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

No annotations are provided, so the description must convey behavior. It only states 'Browser-based tool' and vague references to tax filing, but doesn't clarify how data is input, what the user interaction is, or what the agent should expect when invoking the tool. This is a notable gap for a zero-parameter tool.

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 concise, containing two short phrases in a single line. It front-loads the core function and adds a relevant use case. It could be slightly more structured but is efficient and free of fluff.

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?

Despite being a simple dashboard with no parameters, the description lacks crucial invocation details: what happens when the tool is called, whether it opens a browser UI, returns a report, or requires any state. The 'Browser-based tool' hint is minimal, and without an output schema, the agent cannot anticipate the tool's response.

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?

With zero parameters, the schema offers no semantics. The description compensates by explaining what the tool does overall, though it doesn't describe any specific inputs (since none exist). The baseline for 0 params is 4, and the description meets that by clarifying the tool's purpose.

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 clearly states the tool's function: managing affiliate compensation, PV, and CVR by client and month with graphical representations. It also mentions tax filing use, which distinguishes it from other dashboards by specifying its domain and scope.

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 implies usage for monitoring affiliate revenue performance and tax preparation, providing clear context. It doesn't explicitly mention when not to use it or compare with alternatives like affiliate-revenue-calc, but the dashboard purpose is evident from the description.

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