get_status

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

readOnlyHint=true already declares this as a safe read, so the description only needs to add context beyond that. 'Without fetching messages' usefully signals a lightweight operation that avoids downloading bodies, but there is no mention of performance, caching, or failure modes for a non-selectable folder.

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?

One front-loaded sentence plus a single tight Args line; no filler or restatement of 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?

With an output schema present, return values need not be explained, and the description covers the one parameter's behavior. It is nearly complete for this simple tool, only lacking explicit routing to sibling tools.

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 coverage is 0%, so the description carries the burden for the single folder parameter and does so clearly: a single folder name, or omit for all selectable folders. This adds real semantics (singular name, null means 'every selectable folder') that the bare string/null schema does not convey.

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 and resource ('counts of total and unread messages per folder') and adds the scoping qualifier 'without fetching messages', which implicitly separates it from list_emails/read_email. It does not name a sibling explicitly, so it falls just short of 5.

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 Args note tells the agent that omitting the folder returns every selectable folder, which implies efficient bulk use. However, there is no explicit when-to-use-this-vs-alternatives guidance (e.g. use this instead of list_emails to get counts cheaply).

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