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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is known. The description adds genuinely non-obvious context — the feed is durable and replayable, and reads do not consume events or affect email/webhook delivery — which an agent could not derive from annotations or 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 short sentences, zero filler, with the core mechanism (cursor) front-loaded and the non-consumption guarantee immediately after.

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?

There is no output schema, and the description never says what the feed yields (event records? leads?) or how pagination/cursor advancement works. For a feed-reading tool with three undocumented-in-schema parameters, it is adequate but leaves meaningful gaps an agent would hit on the first call.

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 0%, so the description must carry parameter meaning, and it only explains that the cursor is opaque (and implies replay). The required pipelineId and the limit parameter (1-100) get no explanation at all, and the absence of an explicit statement that cursor is optional / starts from the beginning leaves a real gap.

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 (read) and resource (durable pipeline feed) plus the mechanism (opaque cursor). It's clear what the tool does, but it never distinguishes itself from the closely-named sibling read_pipeline_sample, so an agent must infer the difference.

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?

There is no when-to-use guidance and no mention of alternatives such as read_pipeline_sample or get_pipelines. The only near-guidance is the reassurance that reads don't consume events, which is a behavior note rather than a selection rule.

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