hub_get_dashboard

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

No annotations are provided, so the description carries the full burden. 'Get' and 'Aggregates metrics' clearly signal a read-only operation, which is helpful. It does not discuss potential aggregation latency, data freshness (real-time vs cached), or timeout risk when querying many platforms at once — useful context for a unified aggregator, though its simplicity keeps this from being a major gap.

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 zero waste. The core action and scope are front-loaded in the first sentence, and the second sentence adds the platform detail that reinforces the 'unified' claim. 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 zero-parameter, no-output-schema tool this is nearly complete: it states the purpose, scope, and the platforms involved. The only minor omission is the shape of the returned dashboard, but with no output schema and no parameters, what is present is sufficient for an agent to call it 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?

The tool takes zero parameters, so the description holds no parameter-documentation burden and baseline is 4. The description adds value by telling the agent what data the dashboard contains (cross-platform aggregate metrics and the specific platform list), which is exactly the context an agent needs to decide whether this tool fits.

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 ('Get'), a resource ('unified analytics dashboard') and precise scope ('across ALL connected marketing platforms'), then enumerates the integration targets (WebEngage, CleverTap, Mixpanel, HubSpot, Braze). This clearly differentiates it from the sibling crm_get_dashboard without needing to open either schema.

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 makes the usage context explicit by emphasizing 'ALL connected marketing platforms' — an agent can infer this is the cross-platform rollup, in contrast to tool-specific dashboards like crm_get_dashboard. However, it stops short of explicitly stating when not to use it or naming alternatives, leaving some routing to inference.

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