List Library concepts

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

With no annotations provided, the description discloses pagination, optional family filtering, and the availability of slugs for downstream use. It does not mention output shape or rate limits, but for a read-only listing tool this is sufficient and adds meaningful behavior context.

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?

One concise sentence front-loads the purpose and integrates guidance without waste. Every phrase adds value.

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?

With no output schema, the description still communicates the tool's role, filter options, and how results are consumed (slugs for library_get_concept). It also points to library_search as an alternative, making it sufficiently complete.

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 already covers page/page_size with defaults; description adds that family is optional ('optionally one family') and confirms pagination. With 67% schema coverage, the description helps but family is still only explained via enum values.

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 tool lists all Library concepts, with pagination and an optional family filter. It explicitly distinguishes from library_get_concept and library_search, making its purpose unambiguous.

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 explicit when-to-use guidance: 'Use to enumerate a topic area or find slugs for library_get_concept; for keyword lookup prefer library_search.' This names exact alternatives and gives clear context.

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