search_publications

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

No annotations provided, so description bears full burden. Mentions search across multiple platforms and returns subscriber numbers, but lacks details on pagination, empty results, or rate limits. Minimal behavioral info beyond schema.

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 sentences with no fluff. Purpose is front-loaded, and all details are relevant. Efficient and well-structured.

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 no output schema and moderate complexity, the description covers main operations, query/filter usage, and provides a reference link. However, it does not explain the meaning of 'mode' (default topics) or the structure of returned subscriber data, which are gaps.

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 100%, baseline 3. Description adds value by explaining the relationship between 'query' and 'filters' with examples and a link to full filter reference. This clarifies usage beyond schema descriptions.

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?

Clear verb 'Search' with specific resource 'newsletters' and scope including platforms (Substack, LinkedIn, Ghost, Beehiiv, Kit) and search dimensions (topic, title, author). Also mentions output (subscriber numbers). Differentiates from siblings like search_issues.

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 to specify either 'query' or 'filters' or both, providing clear usage guidance. Does not cover when not to use this tool or alternatives, but the context is clear.

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