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

Annotations already cover safety (readOnly, idempotent, non-destructive). The description adds genuine behavioral context beyond them: 'The excerpt is not the whole page' warns the agent the returned content is truncated, and the layer=beyond note signals a paid-tier boundary. It stops short of describing pagination or exact response shape.

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?

Four compact sentences, front-loaded with the core action before the requirement and caveat details. No filler, though the short sentences have a slightly clipped, note-like rhythm.

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 4-parameter read tool with no output schema, the description conveys the returned payload (summary plus short expanded excerpt) and the truncation caveat. The only gap is that it says nothing about how a missing rank or invalid market/pillar is handled.

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 100%, so all four parameters are already documented, including rank 1-5 default 1 and the layer values. The description largely restates the schema (rank range/default, layer=beyond) with only the minor gloss that beyond equals Attic Beyond, so 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?

The description gives a specific verb and resource: 'Get one ranked name from a weekly pillar pack, with its summary and a short expanded excerpt.' The word 'one' distinguishes it from whole-report siblings like attic_get_market_report, though it never names those alternatives directly.

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?

It states prerequisites ('Requires market, layer, and pillar') and the rank selector, which implies when the tool applies, but gives no explicit when-to-use guidance or routing against siblings such as attic_get_market_report or attic_list_pillars.

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