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

Annotations already indicate readOnlyHint=true and destructiveHint=false, and the description adds valuable context beyond those: it clarifies the return scope (no chapter content) and access rules ('all active loops are navigable by anyone'). This gives an agent useful behavioral expectations without redundancy.

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 tight sentences that front-load the main purpose and immediately specify key limitations and access. Every clause adds value; no filler or unnecessary detail.

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 single required parameter, a rich output schema, and read-only annotations, the description provides everything an agent needs: what it returns, what it excludes, and who can use it. The mention of 'active loops' adds an important boundary condition. No significant gaps.

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 already documents loop_slug with a clear example ('jawz'), and description coverage is 100%. The description only reinforces that the lookup is 'by slug' without adding new meaning or constraints, so it meets the baseline but does not exceed it.

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?

Description uses specific verb 'Get' and resource 'metadata and chapter manifest for a loop by slug,' clearly stating what the tool returns. It explicitly notes it returns 'loop info and the list of chapter nodes with titles — no chapter content,' which differentiates it from content-returning tools like get_chapter.

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?

Provides clear context: this tool is for metadata and titles only, not chapter content, and states that 'all active loops are navigable by anyone,' addressing access. It implies the alternative of using a content-focused tool but does not explicitly name one, so it stops short of a 5.

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