portal_dashboard

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

No annotations are provided, so the description carries the disclosure burden. 'Get' clearly implies a read operation and the content list describes the return payload, but it does not mention authentication expectations, data freshness, or any error/empty-state behavior.

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, direct sentence that leads with the verb and resource, then lists the dashboard contents. Every clause adds useful information and there is no filler.

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 zero-parameter read tool, the description is nearly complete: it names the resource and all main content categories. It could go slightly further by explicitly contrasting with the more detailed sibling tools, but 'main dashboard' and 'highlights' convey enough for correct invocation.

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 input schema is empty and the description makes no parameter claims, so there is no parameter ambiguity to resolve. Baseline 4 applies for zero-parameter tools.

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?

Description uses specific 'Get' plus a clearly named resource, 'main dashboard,' and enumerates the concrete contents returned (student name, pinned items, weekly attendance, timetable highlights). The 'main' qualifier helps distinguish it from focused sibling tools such as portal_attendance and portal_timetable.

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 phrase 'main dashboard' implies this is the high-level overview, while sibling tools cover specific areas, but it does not explicitly state when to prefer this over portal_attendance, portal_timetable, or portal_inbox. Usage context is only implied, not directly stated.

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