list_notifications

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

No annotations provided, so description carries full burden. It discloses useful behavior: account_id auto-resolves if omitted, and pagination details (max page size, 1-indexed). However, it does not state that this is a read-only operation or disclose potential rate limits or side effects, which is a gap.

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?

Description is very concise: one-line purpose followed by a clear bulleted list of parameter details. No redundant sentences; every part adds value.

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 list tool with 5 parameters, no required fields, and an output schema, the description covers all parameter behavior and pagination logic. The output schema handles return value explanation, so no additional detail needed. Complete context for effective usage.

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 and does compensate fully. It explains each parameter: company_id/user_id as optional filters, per_page with max 250, page as 1-indexed, and account_id as auto-resolving. This adds significant meaning beyond the schema's type/defaults.

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?

Description clearly states 'List notification rules on the account' with a specific verb ('list') and resource ('notification rules'). Distinguishes from sibling tools like create_notification, delete_notification, and update_notification.

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?

Description lists optional filters and pagination but does not provide explicit guidance on when to use this tool versus alternatives (e.g., when to use get_notification if it existed). Usage is implied but lacks when-not and alternative recommendations.

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