List DM funnel hits

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

Annotations already declare readOnlyHint=true, so the description adds value by explaining the meaning of a hit and disclosing failure-queue visibility and dmStatus lifecycle. This is context beyond the annotation flags.

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?

The first sentence is information-dense and front-loaded with the resource. However, the final 'CAPABILITY: read' line is redundant with the annotations, making it slightly less concise.

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?

The description lists the output fields, which is helpful since there is no output schema. However, it omits parameter usage and pagination behavior, leaving gaps for a tool with four parameters.

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 0% and the description does not explain any of the four parameters (limit, cursor, status, funnelId). It only mentions 'one DM funnel' implicitly, but no details on filters or pagination.

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 states 'List captured comment evidence and delivery outcomes for one DM funnel' with a specific verb and resource. It includes field details and distinguishes this from sibling tools like list_dm_funnels by focusing on hits for a single funnel.

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 says 'Read-only failure-queue visibility; a hit means a matching commenter, not a verified link conversion,' which sets expectations for when to use the tool. It clearly implies this is for inspecting funnel hits, but does not explicitly contrast with list_dm_funnels or other list tools.

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