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

With no annotations provided, the description carries the burden of behavioral disclosure. It signals a read-only browsing operation, states that results are paginated, and indicates that family filtering is optional. It also implies the output contains slugs usable by library_get_concept, but it does not detail the page response contents or pagination behavior beyond that.

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, front-loaded with the core purpose, and every sentence earns its place. It covers scope, pagination, family filtering, the intended downstream use, and the preferred alternative 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?

Given the tool's low complexity, no output schema, and absence of annotations, the description is sufficient for an agent to invoke it correctly. It covers what the tool enumerates, how it can be filtered, what the output is useful for, and when not to use it.

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 75%, so the schema already documents page, page_size, and context. The description adds meaning by explaining the output intent ('find slugs for library_get_concept') and clarifying that family is an optional filter, going beyond the raw parameter names and 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 specifies a concrete verb and resource: 'Browse every trading and technical-analysis concept in the Library', adding pagination and an optional family filter. It also clearly distinguishes the tool from library_search and library_get_concept, so an agent can tell them apart without inspecting schemas.

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 explicit when-to-use guidance: 'Use to enumerate a topic area or find slugs for library_get_concept' and 'for keyword lookup prefer library_search.' This directly routes the agent to the correct sibling tool for the alternative use case.

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