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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered; the description still adds the key clarification that a quote does not reserve credits and that no spend occurs. Mentioning blocking_errors in the response also surfaces a post-call behavior usefully. It stops short of describing failure modes or quota interactions.

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 short sentences, front-loaded with the core no-side-effect guarantee, then the call sequence. Every sentence carries actionable information with no padding.

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 output schema, the mention of blocking_errors partially covers return values, and the submit_job handoff covers the workflow. However, for a tool with nested, loosely-typed input/settings/billing objects and zero schema descriptions, the definition leaves an agent guessing about the shape of `tool` and `input`, which is a meaningful completeness gap.

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% and all four parameters (including nested open-ended input/settings objects) are undocumented in the schema. The description gestures at 'input/settings' and names a response-side field max_quoted_credits, but never explains what `tool` expects or what billing.max_reserved_credits controls, so the gap is largely unaddressed.

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?

Uses specific verbs (validate, estimate) against concrete resources (scientific input/settings, credits) and explicitly scopes itself as non-submitting and non-spending. An agent can immediately tell this apart from submit_job or get_job without inspecting schemas.

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?

Explicitly gives the workflow: inspect blocking_errors, then pass the accepted amount as max_quoted_credits to submit_job. It names the sibling and the handoff clearly, though it doesn't spell out when quoting is unnecessary or how to handle a rejected quote.

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