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

Adds substantial context beyond the annotations: no model-token cost, results are assembled only from Balford's own published material, each claim cites its source page, and nothing non-public is quoted. It also declares scope boundaries ('not a quotation, a certification claim, or a dimensional acceptance'), which the readOnly/openWorld/idempotent hints do not convey.

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?

Well front-loaded: purpose first, then use cases, then cost and provenance. The final boundary sentence ('not a quotation, a certification claim, or a dimensional acceptance') is denser and more defensive than an agent needs for invocation, but the overall length is reasonable and nothing is redundant.

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?

An output schema exists, so return-value shape need not be explained. Combined with the cost note, sourcing guarantee, and citation behavior, an agent has everything needed to decide to call this tool and to interpret and trust its output.

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 100%, with both 'limit' (range and default) and 'query' (with examples) fully documented in the schema. The description adds no syntax, format, or query-construction guidance beyond that, so the baseline of 3 applies.

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 and resource ('Retrieve the passages of Balford's published engineering material that match a query') and immediately scopes it against the answering sibling with 'without writing an answer.' An agent can distinguish this from ask_balford_engineering without opening either schema.

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?

Gives three concrete use cases: checking what has actually been published, gathering source URLs for citations, and grounding reasoning. The 'without writing an answer' clause implies the alternative answering tool, but no sibling is named explicitly as the recommended route for the opposite case, so it falls just short of full when/when-not routing.

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