update-logs-metric

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

No annotations provided, so description carries full burden. Merely describes the update action without disclosing side effects, permissions, or that other settings might be overridden. Minimal behavioral context.

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?

Single sentence of 10 words, no filler, front-loaded with action and resource. Extremely concise.

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 tool with 4 parameters (one required) and no annotations or output schema, the description is too brief. Does not explain constraints like metric must exist, type restrictions for includePercentiles, or format of filterQuery. Lacks completeness for correct invocation.

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 each parameter having a description. The tool description lists 'filter, group-by, or percentile settings' corresponding to filterQuery, groupBy, includePercentiles, but adds no new meaning beyond schema. Baseline 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 'Update a log-based metric's filter, group-by, or percentile settings', specifying the verb (update) and resource (log-based metric) with distinct aspects. It differentiates from sibling tools like create-logs-metric and delete-logs-metric.

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?

Implies usage for updating existing metrics, but no explicit when-to-use or when-not-to-use guidance. Does not mention alternatives or prerequisites like metric existence.

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