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

With no annotations, the description carries the transparency burden. It indicates the tool is an informational guide producing a certificate type and fields to check, implying a non-mutating lookup. It does not disclose limitations, source standards, or output details beyond that high-level outcome.

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?

One sentence, with the core question front-loaded and a concrete example embedded. Every clause contributes: the inputs, the decision being made, and the output. No filler or redundant restatement of the tool name.

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 two-parameter lookup, this is minimally complete: it states inputs, the decision, and the returned guidance. However, with no output schema and no annotation safety profile, it would benefit from a bit more detail about what exact fields are returned and how it relates to grade_lookup and substitution_check.

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 coverage is 0%, so the description must add meaning. It clarifies that grade and use_case are the inputs determining the result and gives EH36 + shipbuilding as a concrete example. It does not enumerate accepted formats or possible use cases, but the parameter names plus example are enough for basic 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 states a specific purpose: determining which mill cert type applies for a grade and use case, plus which fields to inspect on the cert. The EH36 shipbuilding example makes the query concrete. It is implicitly distinct from the sibling tools grade_lookup and substitution_check because it centers on certificate type selection, though it never names them explicitly.

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 wording implies usage: call this when you have a grade and use case and need the applicable certificate type and fields to check. However, it provides no explicit when-to-use guidance versus grade_lookup or substitution_check, and no exclusions or alternative routing.

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

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

With no annotations provided, the description carries the full burden. It does disclose useful behavior: aliases are accepted and it returns multiple categories of grade information. However, it does not mention output format, error behavior, or whether results are normalized beyond the alias examples.

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?

Two sentences with no filler: the first states the action and output scope, the second explains alias handling with a concrete example. Every part earns its place.

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 single-parameter lookup with no output schema, the description covers the purpose, input semantics, and output categories well. It lacks explicit sibling differentiation and return-structure details, but these are partly covered by the simple nature of the tool and the other dimensions.

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%, so the description must compensate. It does by clarifying that the grade parameter refers to a steel grade and by giving concrete alias equivalents (4140 = 42CrMo4 = SCM440), which adds real meaning beyond the bare schema.

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 uses a specific verb ('Look up') with a clear resource ('a steel grade') and enumerates the return categories: properties, chemistry, forms, applications, weldability. It is clear but does not explicitly differentiate from sibling tools like substitution_check or cert_guide.

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?

No guidance is given about when to use grade_lookup versus the sibling tools substitution_check or cert_guide. The alias behavior is useful, but the description does not state exclusions, prerequisites, or alternative routing.

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

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

With no annotations, the description carries the burden and does disclose useful behavioral detail: it returns a 'verdict + reasoning' and cites 'verified trade rules' as the source. However, it does not address limitations, error cases, or whether the operation is purely read-only.

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 sentence that front-loads the operation, scopes the application, and summarizes the return value. Every clause is informative and there is no filler.

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 simple three-string-parameter tool with no output schema, the description covers the operation, the main input dimension, and the return shape. It could be more complete by defining the possible verdict values, but nothing essential for a first correct call is missing.

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?

Since schema description coverage is 0%, the description must compensate. It adds meaning for 'application' by listing plausible values, and the directional roles of from_grade/to_grade are understandable from the description. It does not specify acceptable grade formats or exact string requirements, so the compensation is only partial.

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 names a specific verb and resource: 'check if one steel grade can substitute another.' It further scopes the operation by application and distinguishes it from siblings like grade_lookup and cert_guide by its substitution-specific function.

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 a given application' with the enumerated categories (machined / welded-structural / pressure) gives clear context for when the tool is appropriate. It does not explicitly state when to use a sibling instead, but the substitution purpose is sufficiently distinct.

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