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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. The only extra information is billing cost ('Billing per call: 1 Credits'), which is cost-related, not behavioral. There is no mention of what the tool returns, side effects, authentication needs, or limitations. This is severely lacking.

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, which might appear concise, but it is under-specified rather than concise. It contains only a tautological phrase, a group label, and a billing note. There is no wasted verbiage, but it is insufficient to be considered effective conciseness; it simply fails to provide necessary information.

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 tool with 6 parameters, no annotations, no output schema, and a complex domain (notifications/mentions), the description is completely inadequate. It provides no context about pagination (cursor), response format, authentication requirements, or how it relates to other notification tools. The description is far from complete for a tool of this complexity.

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?

With 6 parameters and 0% schema description coverage, the description adds no semantic value to the parameters. It mentions none of the parameters (ct0, apiKey, cursor, proxyUrl, resFormat, auth_token), leaving an agent completely in the dark about their purpose, format, or defaults. The description fails to compensate for the schema's lack of detail.

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 'notifications mentions' is essentially a tautology of the tool name, providing no verb or resource clarity. It repeats the name without stating what action the tool performs or what it retrieves. Distinguishing from siblings like notificationsAll or mentionsTimeline is impossible based on this description.

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?

There is no guidance on when to use this tool versus its siblings. The description offers no context, exclusions, or alternatives despite the presence of closely related tools such as notificationsAll and notificationsVerified. An agent would have no basis to choose this tool over others.

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