get_dashboard_data

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the action ('Get') without detailing whether this is a read-only operation, if it requires authentication, what the return format might be, or any rate limits. This leaves critical behavioral traits unspecified for a tool that likely fetches data.

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 extremely concise with just one short phrase: 'Get dashboard data and key metrics'. It's front-loaded and wastes no words, making it easy to parse quickly. Every word contributes directly to the purpose without unnecessary elaboration.

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?

Given the complexity implied by fetching 'dashboard data and key metrics' (which could involve aggregated or varied data), the description is incomplete. With no annotations and no output schema, it fails to explain what kind of data is returned, the structure, or any prerequisites. This leaves significant gaps for an agent to understand the tool's full context and usage.

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 input schema has 0 parameters with 100% coverage, meaning no parameters are documented in the schema. The description doesn't mention any parameters, which is appropriate since there are none. This aligns with the baseline score of 4 for zero parameters, as there's no need to compensate for missing param info.

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 'Get dashboard data and key metrics' states the action (get) and resource (dashboard data/key metrics), providing a basic purpose. However, it's vague about what specific dashboard or metrics are involved, and it doesn't distinguish this tool from sibling tools like get_lead_analytics or get_pipeline_analytics, which might overlap in 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?

The description provides no guidance on when to use this tool versus alternatives. With sibling tools like get_lead_analytics and get_pipeline_analytics available, there's no indication of whether this tool is more general, aggregated, or serves a different context, leaving the agent to guess based on the name alone.

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