Api metrology builtin metric samples refresh create

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

Annotations declare readOnlyHint=false, idempotentHint=false and openWorldHint=true, so a write with external effects is already signalled structurally; the description adds nothing about what is refreshed, whether existing samples are replaced, or what an open-world call might reach out to. It also fails to explain why the operation is non-idempotent.

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 text is one identifier fragment with no sentence structure and no front-loading of intent. It is short, but this is under-specification posing as brevity rather than efficient communication.

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 annotations explaining side effects, no output schema, and no parameter documentation, the description is the only place an agent could learn what this refresh does — and it supplies nothing. An agent cannot safely decide to invoke a non-idempotent, open-world mutation on this basis.

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?

The tool takes zero parameters and the schema coverage is 100%, so there is nothing for the description to disambiguate. Baseline 4 applies for a parameterless operation; the gap here lies in behavioral scope, not parameter meaning.

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 is the raw tool identifier repeated verbatim ("api_metrology_builtin_metric_samples_refresh_create") rather than prose. An agent can only reverse-engineer intent from the snake_case name; nothing states what resource is refreshed, from what source, or with what effect. This is tautology, not a purpose statement.

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?

There is no when-to-use guidance, no prerequisites, and no reference to any sibling despite dozens of adjacent metrology tools (builtin_metric_samples_create, _list, _retrieve, _batch_action_create). Nothing distinguishes this refresh action from a normal create or a batch action.

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