Analytics dashboard

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

Annotations already establish readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds useful behavioral context by indicating the tool opens an interactive visual dashboard rather than simply returning raw data, which is a meaningful behavioral trait beyond the schema.

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?

Two sentences with no filler. The first sentence front-loads the tool's purpose and contents, and the second immediately gives usage guidance and the sibling alternative. Every word earns its place.

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 read-only tool with zero required parameters, a 100% documented schema, and an output schema, the description covers purpose, contents, and usage context. Nothing essential is missing for an agent to decide whether to call it and how.

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%, with both from and to parameters clearly documented including defaults and format examples. The description mentions 'date range' but adds no parameter-level detail beyond what the schema already provides, so the baseline 3 is appropriate.

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 uses a specific verb ('Open') and a clear resource ('interactive analytics dashboard'), then enumerates exactly what the dashboard contains: totals, status breakdown, per-platform stats, and daily post counts. It also distinguishes itself from the key sibling get_analytics by emphasizing the visual/interactive nature.

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 explicitly says to use this tool when the user wants an interactive analytics dashboard and tells the agent to prefer it over get_analytics for a visual view. It names the relevant alternative, though it does not clearly state the condition under which get_analytics should be chosen instead.

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