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

Annotations already establish that the tool is read-only, idempotent, and non-destructive. The description adds meaningful behavioral context by stating that no price, stock, purchase URL, cart, or ordering data is returned, and that only published catalog descriptions are searched. This goes beyond the structured annotations and helps set expectations about the return payload.

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 two sentences with no fluff. The primary purpose is stated immediately, and the second sentence succinctly clarifies the scope exclusions. Every word earns its place, and the structure is front-loaded with the core action.

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 two-parameter search tool with no output schema, the description covers the core purpose and exclusions but leaves important operational details unstated, such as how limit affects results, whether pagination is supported, and what the result format looks like. The lack of an output schema raises the burden on the description to explain return behavior, which it only partially does.

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 has no descriptions (0% coverage), so the description must compensate. It gives some semantic meaning to the query parameter by specifying it searches educational metadata fields, but the limit parameter is entirely undocumented in both the schema and description. No guidance is provided on how limit behaves, default values, or pagination.

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 searches published MyDankTank catalog descriptions for educational metadata, naming specific dimensions (product-format, flavor, lineage, descriptive metadata). It also explicitly excludes commerce data. However, it does not differentiate from sibling tools by name, so some inference is required to distinguish it from search_journal or list_catalog_taxonomy.

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 implies a use case (finding educational catalog metadata) but provides no explicit guidance on when to choose this tool over alternatives like search_journal or list_catalog_taxonomy. There are no when-to-use or when-not-to-use statements, so the agent must infer the appropriate context.

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