_get_sla_metrics

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

No annotations are provided, so the description carries the full burden. It mentions querying a specific data source and returning aggregated metrics, but does not disclose authentication requirements (api_token), potential costs, rate limits, or whether the operation is read-only. The description is minimal for a tool with no annotation support.

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 a single sentence with no superfluous words. It is front-loaded with the core action and resource. However, it could be slightly more structured by detailing parameters or return format.

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 that an output schema exists, the description does not need to detail return values, but it does not mention the return format or time range scope. It covers the high-level purpose but lacks depth on parameter usage and behavioral context.

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 0%, so the description must explain parameters. It explains 'marketplace' (implied by 'for a marketplace') but fails to describe 'window' (default '7d') or 'api_token' (default ''). No additional meaning is provided beyond what the schema names offer.

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 the action ('Return'), the resource ('SLA metrics'), and the specific metrics (avg, p50, p95 sync time in seconds). It also mentions the data source ('BigQuery gold layer'), which distinguishes it from sibling tools focused on DLQ and order operations.

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 implicitly indicates this tool is for retrieving SLA metrics, which contrasts with sibling tools (e.g., _drain_dlq, _retry_failed_sync). However, it does not explicitly state when to use it or when to avoid it, nor does it mention prerequisites.

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