Get dashboard

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

readOnlyHint=true already establishes this is a safe read. The description goes further by naming the payload contents (DMs sent, leads, conversions) and the accepted range modes, which is genuinely useful given there is no output schema. It stops short of noting permissions, timezone, or default behavior when range is omitted.

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 tightly packed sentences with the payload description front-loaded and the parameter rules following immediately. No filler, no redundancy.

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 3-parameter read tool with no output schema, the description covers the metric payload and the range/from/to contract well. The remaining hole is default behavior when range (optional, no required params) is omitted, plus timezone semantics for the ISO dates.

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 carries the burden — and it largely does, enumerating all five range values and specifying that custom requires from/to as ISO dates. The one gap is that 'to' is only covered by the 'from/to' pairing rather than stated explicitly.

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?

States a specific verb+resource ('Dashboard snapshot') and even enumerates the returned metrics (DMs sent, leads, conversions), which is more than the title restates. It does not, however, differentiate itself from the nearby sibling get_analytics, so an agent cannot tell the two apart from the description alone.

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?

Usage is implied through the range enum and the 'for custom, also pass from/to' rule, which tells the agent how to call it in each mode. There is no explicit when-to-use guidance, no statement of defaults, and no routing to or away from alternatives such as get_analytics.

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