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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without the description. The description adds genuine value in the ownership constraint and in scoping the response to an aggregated financial summary, but says nothing about how 'current' values are sourced or whether figures are live vs cached.

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?

A single front-loaded sentence listing the exact aggregates returned, with zero filler or repetition of the title. Every phrase contributes either scope, content or precondition.

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 one-parameter read tool with a full output schema and clear annotations, the description needn't explain return shape; it covers what is aggregated and the ownership scope. The only shortfall is guidance on resolving jobId and on behavior when the job is not owned, which an agent would have to infer.

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 description coverage is 0% for the single jobId parameter, so the description carries the burden of explaining it. It only implies that jobId must reference an owned job and gives no hint about how to obtain a valid id (e.g. via list_jobs), which leaves the compensation incomplete even though jobId is largely self-evident.

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?

States a specific verb ('Returns') and a specific resource (estimate, quote, cost, variation and invoice totals) scoped to 'one owned job', which is far more precise than a generic 'get job' call. It does not name a sibling such as get_job or get_billing_status, so the differentiation is inferential rather than explicit.

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 phrase 'for one owned job' implies a precondition (the caller must own the job) but there is no explicit when-to-use guidance, no statement of when to prefer get_job or get_billing_status instead, and no exclusions. Usage is implied rather than directed.

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