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

No annotations are present, and the description carries the full burden of behavioral disclosure. It fails to mention any side effects, required authentication, rate limits, or what happens on success/failure. Only billing and group are noted, which are not behavioral traits.

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 short, but this is under-specification rather than effective conciseness. It lacks essential information and doesn't structure content front-loaded with useful details. Every sentence is wasted on non-functional metadata.

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 the tool has 6 parameters, no output schema, and no annotations, the description is completely inadequate for an agent to understand the tool's purpose, parameters, or expected behavior. It fails to cover any of the necessary context.

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 schema defines 6 parameters (ct0, apiKey, cursor, proxyUrl, resFormat, auth_token) but the description provides zero explanation of their purpose or format. With 0% schema coverage, the description must compensate entirely, and it does not.

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 simply repeats the tool name ('notifications all') and adds billing/group metadata. It does not state what the tool does (e.g., retrieve all notifications) and is essentially a tautology, offering no distinction from siblings like notificationsMentions or notificationsVerified.

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. Sibling tools with similar scopes exist, but the description gives no context on selection criteria or exclusions.

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