loki_get_phlebo_day_metrics

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

Annotations already indicate readOnlyHint=true and openWorldHint=true, so the description's addition of specific KPI names (Total Assigned, Completed, etc.) provides valuable behavioral context beyond the annotations. It does not contradict annotations.

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 two sentences: the first lists KPIs, the second provides a concise summary phrase. No redundant words, front-loaded with key information.

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 simple 2-parameter read-only tool without an output schema, the description fully explains what the tool returns (specific KPIs). The annotations handle safety and variability. No missing information.

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 coverage is 100% with clear parameter descriptions for date and phlebo_id. The description adds little beyond the schema (e.g., 'on a given date' and 'one phlebo/rider'), so a baseline score of 3 is appropriate.

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 clearly states it provides 'Daily summary KPIs' for a specific rider/date, listing the exact metrics. This clearly distinguishes it from sibling tools like loki_get_phlebo_day_tasks (tasks) and loki_search_phlebo_daily_metrics (search across riders/dates).

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 implies usage for a quick snapshot of a rider's day ('fast how did this rider's day go'). It does not explicitly state when not to use it or mention alternatives, but the context of siblings and the specific KPI focus provides clear guidance.

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