list_notifications

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

The annotations already declare readOnlyHint, idempotentHint, and openWorldHint, covering safety and repeatability. The description adds the context that it lists definitions from a specific table, which is valuable. No behavioral traits are omitted or contradicted.

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?

The description is a single sentence that is front-loaded with the core action and resource. Every word earns its place, with no unnecessary fluff.

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?

While the description covers the essential purpose and table, it lacks details about the return format (e.g., an array of definitions) and any default behavior. Given the simple nature of a list tool, this is adequate but could be more complete to help the agent interpret results.

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?

The input schema provides full descriptions for all 5 parameters (100% coverage), so the baseline is 3. The description adds no additional meaning beyond the schema, but it does not hinder understanding 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?

The description 'List email notification definitions (sysevent_email_action)' clearly states the action (list) and the specific resource (email notification definitions, with the underlying table name). It is precise and distinguishes from siblings like 'list_notification_subscriptions' and 'get_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?

The description provides no explicit guidance on when to use this tool versus alternatives (e.g., get_notification for a single notification, list_notification_subscriptions for subscriptions). There is no mention of when-not-to-use or prerequisites, leaving the agent to infer usage entirely from the purpose.

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