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. Saying 'Read' implies a non-mutating operation, but the description does not address error cases, missing keys, name format, case sensitivity, or what the result looks like.

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 useful examples, no filler, and the core action is front-loaded. It could carry slightly more detail, but as a compact definition it is well structured and easy to parse.

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 read operation with no output schema and no annotations, this is minimally viable: an agent can likely attempt a call. However, return behavior, error handling, and the relationship to sibling tools are missing, so the description is not fully self-sufficient.

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?

The schema documents 'key' with an example but leaves 'name' undescribed, giving 50% coverage. The tool description partially compensates by explaining that the text record is set on a .hood name and giving key examples, but it still does not fully define the expected 'name' format or allowed key values.

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 clear action, 'Read a text record', and ties it to a specific resource, a .hood name, with concrete key examples. It does not explicitly distinguish itself from siblings like resolve_name or reverse_resolve, but the resource and action are identifiable enough.

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 intended use is implied: call this when you want to read text records stored on a .hood name. However, there is no explicit guidance about when to prefer this over the sibling tools, nor any exclusion criteria.

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