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

Annotations already mark this as read-only and idempotent, and the description adds useful context: the operation is free, unmetered, returns content verbatim, and is intended to be fetched once and reused. This aligns with the annotations and enriches them without contradiction.

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 compact and well-ordered: purpose first, then cost/behavior, then practical usage. Every sentence earns its place, and the backticked tool references make the intended workflow clear without extra words.

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 simple read-only reference tool with one optional parameter and no output schema, the description is largely complete: it states what is returned, that it is free and unmetered, and how to use it with downstream tools. It does not specify the exact output format, but the source-reuse instruction mitigates that gap.

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 input schema covers the single optional parameter fully, including the enum values and the note that omitting it returns all three stages. The description mentions evaluation, remediation, and harvest but does not add meaning beyond the schema, so the baseline of 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 clearly states a specific verb and resource: it returns the SHPBL disciplines verbatim, plus verification axes and reporting style. It is specific and unambiguous, but it does not explicitly distinguish itself from sibling tools like library_document or library_index, so it stops short of full differentiation.

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 gives practical usage guidance: fetch once and then call fix_repo or harvest_repo with brief: true so the payload is source rather than repeated instructions. It provides clear context and names related tools, though it does not explicitly state when not to use this tool.

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