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

Annotations already declare readOnlyHint: true, and the description reinforces this with an explicit 'READ-ONLY: this call changes nothing and can be repeated safely.' It adds behavioral detail beyond annotations with pagination semantics ('oldest first, paged by since_id until has_more is false') and the set of event types returned. No contradiction with the annotation.

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 description is dense but purposeful: it front-loads the core purpose, packs the event list, paging logic, doorbell relationship, and read-only safety into three sentences. Some domain phrasing ('mine', 'doorbell', 'ring') may be cryptic to newcomers, but nothing is wasted.

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, so the description must explain what the response contains. It covers ordering and pagination and names event types, but it does not describe the row/record shape, fields per event, or the role of the secret parameter. For a 2-parameter tool with zero schema coverage and no output schema, this leaves meaningful 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 description coverage is 0%, so the description must compensate for both parameters. since_id is given meaning as a pagination cursor, but no format, default, or required-ness is explained. secret is never mentioned at all, leaving a required-sounding authentication parameter completely opaque.

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 the resource ('money rail') and the verb-like action ('What moved for you...') with enough specificity to understand it returns events for the caller. The enumeration of concrete event types (submission.received, award.created, etc.) makes the purpose concrete. It does not explicitly compare to sibling tools like 'events' or 'history', but the 'money rail' framing separates it from generic event objects.

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 provides a clear trigger: 'A mine doorbell rings when a row lands here for you; this is what the ring tells you to read.' It also explains how to page through results using since_id until has_more becomes false. It does not name alternative tools or give explicit when-not-to-use guidance, so it falls short of a 5.

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