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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description's added content is essentially return-value shape, which is already carried by the existing output schema, so it contributes little behavioral context beyond structured data.

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 that states the return and its constituent parts, with no wasted preamble. The trailing colon list is slightly long but each item is informative rather than 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?

An output schema exists, so return values need not be explained, and annotations cover safety — but in a 27-sibling toolset the definition omits which page types this generic fetch is for versus the specialized getters. For a tool whose main risk is misrouting, that gap keeps it at minimum viable.

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% and the single 'id' parameter is richly documented with example values in the schema itself. The description's 'identified by its id' restates that without adding format or validation meaning, so the baseline 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 concrete verb ('Returns the full text') and an unambiguous resource ('one Craft Quantities page, identified by its id'), and even sketches the content shape (what it works out, inputs/measurements with units, opening values, sources). It does not, however, differentiate itself from page-type-specific siblings like get_calculator, get_takeoff, or get_sources, whose overlap is left unaddressed.

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 when-to-use or when-not-to-use guidance. With 27 siblings, several of which (get_calculator, get_takeoff, get_sources) appear to retrieve the same underlying page data in a narrower form, an agent gets no rule for choosing 'fetch' over them. Usage is only implied by the generic name.

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