schoolmail_folders

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

No annotations are provided, so the description carries the full behavioral burden, yet it only says mailboxes come with message counts. It never states that this is a read-only operation, what account or auth scope it operates against, or whether the counts are total versus unread — all of which matter for a mail tool with no annotation coverage.

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 short sentence with no filler, and the resource is front-loaded. It is efficient, though arguably too terse to be fully front-loaded with actionable intent since no verb anchors the sentence.

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?

An output schema exists, so return values need not be explained, and the zero-parameter signature keeps invocation trivial. However, with no annotations and heavy sibling overlap, the description leaves the read-only nature and the distinction from outlook_folders unspecified.

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 tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. No parameter-related gap exists.

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 phrase 'School account mailboxes with message counts' identifies the resource and a hint of the content, but omits the verb entirely — an agent must infer this is a listing operation. It also fails to distinguish itself from the sibling outlook_folders, which sounds like the same kind of resource.

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 statement of when to use this tool versus outlook_folders, schoolmail_search, or schoolmail_read. The agent is left to guess whether this is a discovery step preceding a read or a standalone listing call.

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