browse_reading_room

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

Because there are no annotations, the description carries the full burden of behavioral disclosure. The verb 'List' implies a read-only operation, and the genre qualifier adds useful curation context. However, it does not mention authentication, rate limits, return format, or whether only metadata is returned versus full text.

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?

The description is a single, front-loaded sentence that immediately states the action and resource. Every phrase earns its place by adding scope or purpose without redundancy.

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 zero-parameter browse tool, the description is largely complete: it names the resource, the content categories, and the intended AI activity of encountering and annotating. It could be more complete by specifying what the returned list contains, but the absence of parameters and output schema makes the current description sufficient for a basic call.

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 tool has zero parameters, so the baseline for this dimension is 4. The description adds contextual meaning about the content being listed even though there is nothing to document at the parameter level.

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 opens with a specific verb and resource: 'List texts available in The Reading Room.' It further distinguishes the tool by naming the curated content types—poetry, philosophy, and letters—which separates it from sibling browse tools like browse_voices or browse_postcards.

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 would call this to see what texts are available before reading or annotating. However, there is no explicit statement of when to prefer this over related tools such as read_text or suggest_text, and no when-not-to-use guidance.

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