usage

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

No annotations are supplied, so the description carries the full behavioral burden, and it discloses almost nothing. The word 'preview' weakly implies a non-mutating read, but authentication needs, account/workspace scoping, time window for the usage figures, and whether the pricing shown is authoritative are all unstated.

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 brief and front-loaded with no filler, but it is a noun phrase without a verb, so its brevity reflects under-specification rather than efficient writing. A single additional clause naming the action would have made it useful at nearly the same length.

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, no parameters, and no output schema, the description is the only source of information about this tool, and it does not say what data comes back, over what period, or for which account. For a tool whose output is entirely unfamiliar, this leaves the agent unable to decide whether to call it.

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 input schema defines zero parameters, so there is nothing for the description to clarify; the baseline for a no-parameter tool applies. The implicit absence of any scope or date argument is not explained, but that is a minor gap rather than a parameter-documentation failure.

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?

"Your usage and draft pricing preview" is a label fragment, not a statement of what the tool does. It hints at two outputs (usage data and a pricing preview) but supplies no verb and no indication of what 'usage' covers or what the tool actually returns, so the agent must guess from the name alone.

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 exclusions, and no reference to any sibling such as weave_ask, weave_reference, or search. The agent has no way to know whether this is a billing lookup, a quota check, or a plan-comparison aid, or when to prefer it over the other eight tools.

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