get-metering-job

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'Get complete information' without revealing whether it is read-only, what response format to expect, or any side effects/requirements. This is a significant transparency gap for a get operation.

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, concise sentence with no fluff, but it is under-specified. It is structurally minimal but fails to convey essential information, making it borderline between efficient and insufficient.

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 there is no output schema or annotations, the description should explain what 'complete information' includes, any pagination, or error behavior. It does none of these. The tool's simplicity (one param) lowers the bar, but the description is still too thin to be considered complete.

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 has one parameter (job_id) with zero description coverage, and the description does not mention this parameter at all. The agent must rely solely on the parameter name, which is somewhat self-explanatory but the description adds no value in clarifying the parameter's meaning, format, or usage.

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 ('Get') and resource ('complete information for a metering job'), and the word 'complete' distinguishes it from sibling tools like get-metering-job-status and get-metering-job-result, which focus on specific aspects. This is a specific and helpful 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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention that this is the full-detail counterpart to status/result tools, nor does it offer any exclusions or conditions. The agent is left to infer usage from the name and sibling list.

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