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

With no annotations provided, the description carries the full burden, and it delivers: it reveals server-side counting (no client-side paging), exact-match requirement with rejection of guessed spellings, the 'withoutBibleRef' caveat, and that distributions are truncated to most-frequent entries and say when they omit data. No hidden surprise about what gets counted or omitted is left unstated.

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 front-loaded with the most important distinction ('counts only, never the items themselves') and uses compact sentences. It is a little dense and re-states the exact-match rule already in the schema, but every sentence contributes either behavior, usage guidance, or a caveat, so nothing feels wasted.

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 that an output schema exists and there is only one parameter, the description is complete: it states what the tool returns, what it does not return, its caveats, its prerequisites, and when to choose it over a sibling. An agent has everything needed to invoke it correctly and interpret its results.

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 description coverage is 100%, and the schema already explains that 'topic' must be exactly as listed by crossload_browse with the rejection consequence. The description repeats this rather than adding new parameter-level meaning, so it stays at the baseline: useful reinforcement, but no substantial semantic addition beyond the schema.

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 explicitly states the tool 'returns counts only, never the items themselves' and then enumerates the exact distribution dimensions (bible books, authors, series, years, etc.). It also names the sibling tool crossload_search as the place to go for the actual items, making the tool's scope unmistakable.

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?

It gives concrete use cases: answering which passages/authors/years a topic spans, finding related topics by evidence, and summarizing a topic before writing. It also names the alternative (crossload_search for item-level results) and states a prerequisite: the topic name must match crossload_browse exactly.

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