alphaportal_list_notifications

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

Annotations declare readOnlyHint=true, and the description's 'List' is consistent. The description adds useful context about return content (title, body, student, timestamp) beyond the annotation, though it does not mention auth, rate limits, or ordering—minor for a read-only list.

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?

Single sentence, front-loaded with the action, then specific details. No unnecessary words or redundancy.

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 simple read-only list with no parameters and no output schema, the description sufficiently specifies what notifications are returned and their fields (title, body, student, timestamp). It omits mention of ordering or pagination, but these are not critical for a no-parameter retrieval tool.

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?

Tool has zero parameters, so the baseline is 4 per the rubric. The description's mention of the returned fields provides contextual value but does not need to explain parameters since none exist.

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?

States a specific verb (list), resource (account's transportation notifications), and clarifies the content (arrival/departure alerts with fields). Distinguishes from siblings by focusing on notifications rather than students, schools, or other resources.

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?

Purpose is clear enough that an agent knows when to call this tool—whenever notifications need to be retrieved. No explicit alternatives are mentioned, but the context is unambiguous given the sibling set, and no conflicting tool serves the same purpose.

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