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

readOnlyHint=true already covers the safety profile, and the description still adds real behavioral context an agent couldn't infer: Slack/Teams webhook URLs are redacted and the payload contains personal data. It also enumerates the returned fields, which matters since there is no output schema. It stops short of describing pagination behavior or result ordering.

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?

Front-loaded with the action and resource, then return fields, then the redaction/PII caveats — good ordering with no filler. The trailing "Sorry: GET /v1/pages/{page_id}/subscribers" is mildly redundant given the name and page_id parameter but does help confirm the underlying resource.

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 five parameters, no output schema, and read-only annotations, the description carries appropriate weight: it enumerates the return fields and flags redaction and PII, which is exactly the gap an absent output schema leaves. Pagination and sorting behavior are the only notable omissions, and the schema covers paging 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 description coverage is 100%, so all five parameters (page, per_page, include, page_id, component_id) are already documented in the schema, including the caveat that component_id also returns subscribers subscribed to all components. The description adds no parameter-level meaning beyond that, so this sits at the baseline.

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 ("List a status page's subscribers") and immediately scopes what a subscriber is ("people and channels notified of notices"), which separates it from the singular sorryapp_get_subscriber and the create/update siblings. The trailing API route anchors the resource unambiguously.

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?

Usage is only implied: listing subscribers for a page. It gives a useful chaining hint that page_id comes from sorryapp_list_pages, but never says when to prefer this over sorryapp_get_subscriber or how to narrow results (e.g. use component_id for a subset). No exclusions or alternative routing.

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