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

The description provides no behavioral insights such as pagination, filtering behavior, or authentication requirements beyond what the name implies. With no annotations, the description carries full burden but fails to disclose any 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?

While extremely short, the description is under-specified rather than concise. It fails to earn its place by adding value, consisting of three words that repeat the tool name.

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 no output schema and no annotations, the description is severely incomplete. It omits details about response format, authentication (implicit via rider_token), and filtering options, leaving major gaps.

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 adds no meaning to the parameters. Schema coverage is 50% (only rider_token has a description), and the description does not clarify the 'unreadOnly' parameter or its impact on results.

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 'Get your notifications' is a clear verb+resource pair, but it is tautological with the tool name and does not distinguish from sibling tools like 'get_channel_messages' or 'get_follow_counts'. It adds minimal specificity beyond the name.

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. There is no mention of prerequisites, exclusions, or usage context, leaving the agent to guess.

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