get_context

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

No annotations are provided, so the description carries the full behavioral burden. "Read" weakly implies a non-mutating operation, but nothing is said about permissions, whether the envelope is cached or freshly computed, or what "canonical" implies in terms of freshness or resolution.

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 is appropriately front-loaded and wastes no words, but here the brevity reflects under-specification rather than disciplined concision — the one sentence is the entire content of the definition.

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. Still, with zero annotation coverage, an undocumented parameter, and heavy reliance on undefined jargon, the definition is not complete enough for an agent to call this correctly without guessing.

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% for the single required hydration_id parameter, so the description must compensate. It only echoes the concept ("a hydration identifier") without giving format, source, or how to obtain a valid value, adding essentially no meaning beyond the parameter name.

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?

"Read the canonical envelope for a hydration identifier" gives a verb (Read) and an object (canonical envelope), so it is marginally more than a tautology. However, "hydration identifier" and "canonical envelope" are undefined internal jargon, so an agent cannot confidently distinguish this from siblings like hydrate_message or resolve_resource_version.

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?

There is no when-to-use guidance, no prerequisites, and no mention of any alternative tool. The agent is left to infer the relationship to hydrate_message and the other hydration-related siblings entirely on its own.

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