get_kpi_dashboard

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

No annotations provided, so description carries full burden. It mentions API key requirement but lacks details on read-only behavior, rate limits, or data refresh frequency. Does not disclose if the dashboard is aggregated or real-time.

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, no redundancy. First sentence immediately states purpose, second adds important access constraint. Every word contributes.

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?

With no parameters or output schema, description is minimal. It covers purpose and access but omits output format, interpretability, or integration hints with sibling tools. Adequate for a simple tool but could be more helpful.

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?

Zero parameters; schema coverage is 100%. Description adds value by explaining the dashboard content ('targets vs actuals for all key supply chain metrics') beyond the empty schema. Baseline score of 4 applies.

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?

Description uses specific verb 'Get' and resource 'KPI performance dashboard', clarifying scope as 'targets vs actuals for all key supply chain metrics'. It distinguishes from sibling tools like get_financial_metrics or get_optimization_recommendations.

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?

States 'Premium tool. Requires API key' as a constraint but does not explicitly say when to use this tool versus alternatives like check_stock_levels or get_order_statistics. Usage context is only implied.

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