deployment_get_billing_metrics

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered elsewhere. The description adds only the raw REST path (GET /deployment/api/billing-metrics), with no disclosure of aggregation window, default time range, or response shape for a metrics endpoint.

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?

Three very short lines, front-loaded with the action and scope. The first line duplicates the tool name and adds nothing, but total length is minimal and the endpoint line is cheap context.

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?

No output schema exists, so the description must carry the burden of explaining what a 'billing metric' looks like — and it does not: no time window, no units, no dimensions, no pagination. For a metrics retrieval tool this leaves the agent unable to predict the result or judge whether it answered the question.

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, so the baseline is 4. The phrase 'for current org' usefully confirms that org scope comes from the session context rather than an argument, which is the only semantic gap a zero-param tool could have.

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 verb+resource (get billing metrics) is stated, and 'for current org' adds a scope qualifier that separates it from the resource-usage metrics siblings. However, the first line merely restates the tool name, and the description never says what kind of billing data (cost, spend, chargeback, period) is returned, so the purpose stays at a surface level.

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 guidance on when to call this versus the many metrics_get_resource_usage_metrics* and deployment_get_deployment_expense_history_by_id siblings. The only usage signal is implicit in 'current org', which hints that no org identifier is needed.

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