publisher_directory

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

No annotations provided, so description must cover behavior. Reveals HTTP GET, public access, and return fields (pagination, counts, pricing, sample articles). Lacks mention of rate limits or caching but adequate for a browse tool.

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?

Two concise sentences plus filter note. Front-loaded with endpoint and value proposition. Every sentence adds necessary info 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?

No output schema or annotations. Description explains return content (publishers with pricing, samples), pagination, filters, and auth status. Could mention default pagination values or error handling, but sufficient for a browse tool with 5 params.

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 100% (baseline 3). Description adds context: category is case-insensitive substring, min_articles filters by licensable articles, verified defaults to 'true'. Adds value beyond 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?

Description specifies verb 'Browse' and resource 'public Opedd publisher catalog' via endpoint. Clearly distinguishes from sibling 'browse_registry' which lists licenses.

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?

Explicitly states primary use: 'discovery surface for AI labs to find Opedd-licensable publishers'. Contrasts with browse_registry (licenses). Notes public no-auth for pre-purchase scoping.

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