dashboard_kpis

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

No annotations are provided, and the description only mentions 'KPIs' without disclosing any behavioral traits such as whether the data is cached, real-time, or requires permissions. The description carries the full burden but provides minimal transparency.

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 short (three words), which is concise but provides little information. It is not verbose, but its brevity limits usefulness. For a zero-parameter tool, it is minimally acceptable.

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 zero parameters and no output schema, the description should explain what KPIs are included or how they are presented. It fails to do so, leaving the agent without necessary context for proper invocation or interpretation.

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?

There are no parameters, so the description does not need to add parameter semantics. The schema coverage is 100% trivially, but the description could still explain the output, which it does not. Baseline 3 is adjusted to 4 due to zero parameters, though improvement possible.

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 'KPIs du dashboard principal' indicates it returns KPIs of the main dashboard, but does not specify which specific metrics or how they are structured. This provides a general purpose but lacks detail needed for precise understanding.

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?

No guidance is provided on when to use this tool versus alternatives like 'dashboard_alerts' or 'stock_dashboard'. The description does not differentiate its use case from siblings.

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