notifications

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

The description indicates a read operation with 'Gets', but no annotations are present. It does not disclose authentication needs, rate limits, pagination, or the output structure, leaving significant behavioral gaps.

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 very short and gets to the point. The structure uses an 'Args' section for parameter details, which is clear. However, it could be more concise by removing redundancy (e.g., 'Args:' is implied).

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?

The tool has an output schema but the description does not mention return values or format. Given the complexity of notifications and many sibling tools, the description should explain what data is returned, any ordering, or batch size limits.

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 description explains the sole parameter 'count' with its purpose ('Number of notifications to retrieve') and default value (20), adding meaning beyond the schema which only provides title and type. Schema coverage is 0%, so description compensates well.

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 clearly states the tool gets account notifications and alerts, using the verb 'Gets' and specifying the resource. It distinguishes from sibling 'latest_notification' by being plural, implying a list retrieval.

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 is provided on when to use this tool versus alternatives like 'latest_notification' or other notification-related tools. The description lacks explicit context for usage conditions or exclusions.

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