list_self_notifications

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

No annotations are provided, so the description carries the full burden. It discloses pagination but does not mention authentication, rate limits, side effects (none expected for listing), or what constitutes a 'self-notification'. Additional transparency about the return format would be beneficial.

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 extremely concise with two sentences: one for purpose and one for key behavior (pagination). Front-loaded and no fluff, every word earns its place.

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?

Given zero parameters and no output schema, the description is adequate but lacks context about the return structure beyond 'paginated results array'. It does not specify what fields each notification contains, which could hinder an agent's ability to use the output effectively. More detail on the response shape would improve completeness.

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 has zero parameters and coverage is 100%, so the description does not need to add parameter details. Baseline for 0 parameters is 4, which is appropriate as no additional parameter context is required.

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 the verb 'List' and resource 'self-notifications', adding version '(platform notification v1)' and mentioning paginated results. This distinguishes it from sibling tools like 'get_self_notification' (single) and 'create_self_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 implies usage for listing all self-notifications but provides no explicit guidance on when to use this tool versus alternatives like 'get_self_notification' (for a single notification) or 'create_self_notification'. No exclusions or context are given.

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