What's new in ProBo

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered. The description adds the useful fact that results span three distinct content types, but says nothing about ordering, per-source vs. total limits, or how much is returned per source.

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 tight sentence, front-loaded with the 'What's new' framing and immediately followed by the concrete contents. The only minor redundancy is restating the title's phrase 'What's new'.

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 no explanation, and the tool is low-complexity with one optional parameter. What remains missing is the semantics of the limit parameter, which neither the schema nor the description supplies.

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% for the single 'limit' parameter, so the schema supplies no meaning beyond type and bounds (1-50, default 5). The description's 'the latest' hints at truncation but never clarifies whether limit applies per content type or across the combined result set, which is exactly the ambiguity an agent needs resolved.

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 names a specific resource and enumerates the three content sources it aggregates (inbox messages, news posts, recently added documents), so the agent understands it is an aggregate 'what's new' view rather than a single-entity fetch. It does not, however, explicitly contrast itself with the sibling list_messages, list_news, or recent_documents, leaving some ambiguity about when the aggregate is preferable.

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 explicit when-to-use statement, no exclusions, and no named alternative among the many siblings. An agent must infer from the phrase 'What's new' that this is a dashboard-style summary rather than a filtered list call.

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