read_three_tiers

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

No annotations are provided, so the description carries the burden. It implies a read-only static doc fetch, but says nothing about return format, length, or whether the file always exists. For a zero-parameter documentation read the risk is low, so this is an acceptable but not rich disclosure.

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 naming the file and immediately summarizing its contents. No 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?

For a trivial static-document read with no parameters, no annotations, and no output schema, the description gives enough to know what comes back (the three authoring tiers). Only minor gaps, such as the file's scope or format, are left open.

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 has zero parameters, which is the documented baseline for a 4. The description correctly implies no arguments are needed to fetch the file.

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 (Return) and resource (THREE-TIERS.md), then clarifies the content: the three authoring tiers (mixin / utility class / bare tag). This distinguishes it from sibling doc readers like read_theming or read_llm_txt, though it doesn't explicitly contrast them.

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?

Usage is implied: an agent should call it when it needs to understand the mixin/utility-class/bare-tag tier model. There is no explicit when-to-use, when-not-to-use, or named alternative among the many read_* siblings.

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