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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds only that the complete (not partial) content is returned; it says nothing about pagination, truncation, auth requirements, or failure behavior for invalid ids.

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 with no filler: verb, resource, scope, and id provenance in one pass. Nothing is redundant or 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?

For a one-parameter read tool whose annotations already cover the safety profile, this is nearly sufficient: the agent knows what it retrieves and what to pass. The only gap is that with no output schema, nothing describes the shape or size of the 'full content' returned.

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?

With one parameter at 100% schema coverage the baseline is 3, and the description adds real meaning by stating where the id comes from (the return of search) and that a short code is acceptable via the schema. This provenance hint helps the agent supply a valid value rather than just naming the field.

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 (fetch) and a specific resource (the full content of a ContexteTech resource), and pins the identifier's origin to search results. It differentiates itself from the search siblings, though it does not explicitly distinguish itself from the similarly named load_resource or get_download_link.

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 'by the id returned by search' implies the correct usage context and chains this tool after search, which is helpful. However, there is no explicit when-not guidance and no comparison against load_resource, which sounds like a plausible alternative for retrieving a resource.

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