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

The description discloses behavior the annotations don't: a hit writes plan and status onto the matching contact, and `create` can spawn a new contact. That explains the readOnlyHint=false and destructiveHint=true. It still doesn't flag that stamping may overwrite existing contact fields or mention latency/rate limits of a live Substack read.

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?

Three tight sentences, with the core question ('is this address a subscriber') front-loaded before the side-effect clauses. Slightly dense phrasing but nothing extraneous.

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?

With only 2 params, no output schema and no nesting, the description covers purpose, side effects and the create flag well. The gap is return shape — 'a hit' implies a boolean/result but the description never says what comes back.

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%, so baseline 3. The description adds real nuance for `create`: it only takes effect on a hit and only when nobody already holds the address — more precise than the schema's 'Create the contact when the address is new.'

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?

States a specific verb and resource ('Whether one email address subscribes to the user's Substack, read from Substack right now') and adds scope detail — live read, contact stamping, optional contact creation — that separates it from list-style siblings like get_substack_subscribers or import_substack_subscribers.

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?

Gives an explicit usage framing ('Use it for "is x@y.com a subscriber?"'), which is clear context for invocation. It does not, however, name competing tools such as get_substack_subscribers or import_substack_subscribers or say when to prefer them, so it stops short of full routing guidance.

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