substack_explore

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

With no annotations, the description carries the full burden, and it delivers: it discloses the heterogeneous module structure, enumerates known module types, notes that only populated collections are returned, and explains cursor-based pagination with early curated shelves versus later individual Notes/posts. This gives an agent a strong behavioral model beyond the bare 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?

Every sentence earns its place: the first two state what the tool does, the next explains the non-flat structure, the module-type enumeration is dense but necessary, and the final sentence covers population and pagination. It is front-loaded and free of filler.

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 tool with no output schema and no annotations, the description covers the key operational aspects: return shape (modules with types), module variations, and pagination behavior. It does not explain what happens when no parameters are provided or how to obtain tab/type values, but the schema already references the tabs endpoint, so the missing pieces are minor.

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%, so the schema already documents tab, type, and cursor. The description adds context for cursor by explaining pagination is cursor-based, but it does not elaborate on tab/type semantics beyond what the schema provides. This matches the baseline of 3 for fully covered schemas.

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 opens with a specific verb and resource ('Browse the public Substack Explore surface') and immediately clarifies it returns one page of that surface. It distinguishes itself from the many sibling Substack tools by naming the Explore surface and describing its heterogeneous module structure, making it clear this is not a flat list or a notes/publication endpoint.

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 solid context about what Explore is ('a feed of heterogeneous modules rather than a flat list') and how pagination behaves, but it never explicitly states when to choose this tool over alternatives like substack_categories or substack_notes. Usage is implied rather than stated, and no exclusions or alternative routing are provided.

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