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

The readOnlyHint annotation already declares the operation is read-only, so the description need not repeat that. It adds contextual value by explaining what these subscriptions receive, but does not disclose behavioral traits like pagination, ordering, or response structure. Given the annotation coverage, this is adequate but not rich.

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 sentences, both informative: the first states the exact action and resource, the second clarifies the domain context. No filler or redundant phrasing, and the key purpose is front-loaded.

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?

For a simple list tool with pagination parameters, the description is sufficient. It identifies what is listed and the nature of the subscriptions. While it does not explicitly state the return format or mention that results are paginated, the schema's page/size parameters imply this. No output schema exists, so the description carries a light burden.

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% for both parameters (page and size) with defaults and bounds. The description adds no parameter-specific information beyond what the schema provides, so the baseline of 3 is appropriate.

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 opens with the specific verb 'List' and resource 'platform event webhook subscriptions', clearly distinguishing this from sibling tools like get, save, delete, and test. The second sentence adds context about what these subscriptions are (deployment lifecycle notifications), making the purpose unambiguous.

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 implied rather than explicit: the description says 'List...' which suggests enumerating all subscriptions, but it does not contrast with the get tool for retrieving a single subscription or mention when one should prefer list over alternatives. No exclusions or when-not guidance is provided.

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