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

The description describes a read/inventory operation ('List all active...'), yet annotations declare readOnlyHint=false and idempotentHint=false, which assert a non-read, non-idempotent operation. That is an annotation contradiction: an agent relying on the hints would assume listing mutates state. The only behavioral value added is the explicit 10-credit (Tier 1) cost, which is real but does not offset the inconsistency.

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?

A single tight sentence with the scope qualifiers front-loaded, plus compact [Group] and [Cost] tags that carry genuinely useful operational metadata. Nothing is wasted, though the single sentence is arguably thin for a listing tool that may paginate or return large result sets.

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?

An output schema exists, so return values need not be described, and the cost tag covers billing. However, for a list endpoint there is no mention of pagination, result limits, or ordering, and the read-only/annotations conflict leaves the agent unsure whether the call is safe — a meaningful gap given the tool's sibling set.

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 the schema already fully documents `fields` (compact-mode dotted paths) and `precision` (decimal rounding). The description adds nothing about either parameter, so the baseline 3 is appropriate; no parameter meaning is lost, but none is contributed either.

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?

Names a specific verb ('List') and resource ('webhook subscriptions') and narrows scope to 'active' subscriptions 'for the authenticated user', which distinguishes it from siblings like astroway_webhooks_subscribe (create) and astroway_webhooks_id (single record). It is clear and specific, though it never names those siblings explicitly.

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 / when-not-to-use guidance and no alternative named, even though the sibling set contains an obvious complement (astroway_webhooks_subscribe to create, astroway_webhooks_id to fetch one, astroway_webhooks_id_test to test). The agent must infer that this is the discovery/inventory call. Scope of 'active' is stated but not what makes a subscription inactive.

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