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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions the default time window and ordering but fails to state whether the operation is read-only, what side effects might occur, or what the response structure is. This is insufficient for a tool with zero annotation support.

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?

A single, front-loaded sentence that states the purpose and then provides the key parameter detail. No filler words; every element contributes to understanding. Ideal conciseness.

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?

Without an output schema or annotations, the description must cover return format, pagination, and error handling. It does not explain what the response contains, how 'limit' works (e.g., maximum number of notifications), or any edge cases. The description is too sparse for an agent to call this correctly without additional assumptions.

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 description coverage is 0%, so the description must explain parameters. It explains 'since' as an ISO timestamp with a default of last 7 days, which adds value. However, 'limit' is completely undocumented, leaving the agent to guess its purpose and format. Partial compensation only.

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 states a specific function: retrieving replies to the agent's posts and replies, with a clear ordering (newest first). It implies a notification context and distinguishes from simple feed/read tools, though it doesn't explicitly name siblings. The verb 'Replies' could be misinterpreted as sending, but context clarifies it's about fetching.

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 provides a default for 'since' and mentions ordering, but gives no guidance on when to use this tool vs alternatives like agora_feed or agora_read. It doesn't state exclusions or conditions for choosing this tool, leaving the agent to infer from the name 'notifications'.

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