List Notification Profiles

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

The annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the description's 'read-only' note merely repeats structured data. The only novel-ish phrase, 'via the engine', is too vague to convey behavior; no mention of pagination, permissions, or scoping by domain.

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 labeled bullets, front-loaded with purpose, no filler sentences. The templated '**Purpose:**'/'**Side effects:**' framing is a touch formulaic but wastes no words.

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 one-parameter, read-only list tool with no output schema, the description is minimally sufficient, but it omits anything about the return shape or result set scope. An agent could call it, but with no more understanding than the schema and annotations already provide.

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 the single 'domain' parameter, so the schema carries the meaning and the description need not compensate. Baseline 3 applies; the description adds nothing about how domain scopes the listing.

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+resource ('List Notification Profile profiles') and the 'List' verb distinguishes it from its notification.get/create/update/delete siblings. The phrasing is slightly redundant ('Profile profiles') but the intent is 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?

No guidance on when to use this versus siblings like notification.get or the other *.list tools. Usage is only implied by the verb 'List'; there are no prerequisites, exclusions, or alternatives named.

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