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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds valuable context beyond annotations: the content catalog, update cadence (new piece every two weeks), and exactly what is returned in each mode (token lengths in list, markdown in full). It does not disclose error behavior or auth needs, but those are not critical here.

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?

Two tightly written sentences front-load the content catalog and then specify the conditional behavior. Every clause earns its place, with no redundancy or 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?

Given the read-only annotations, 100% schema coverage, and absence of an output schema, the description is largely complete: it explains content, both modes of operation, and return format. It could mention what happens if an invalid 'piece' is supplied, but that is a minor gap for a simple read tool.

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 the baseline is 3. The description adds meaning beyond the schema by explaining that the list includes token lengths and that the full piece is returned as markdown. This clarifies output format and list content, which the schema alone does not convey.

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 clearly states the resource (short works for the campus) and the two modes of operation: listing pieces with token lengths, or returning a single piece in full as markdown. It does not explicitly differentiate this tool from similar siblings like read_the_commons or sit_with_a_work, so it falls short of a 5.

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 description implies usage through its conditional behavior (without 'piece' lists, with 'piece' returns the item) but offers no explicit guidance on when to choose this tool over alternatives. There are no exclusions or named alternatives, leaving the agent to infer from context.

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