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

The annotation provides readOnlyHint=true, and the description aligns by implying a read-only browsing action. It adds context about the type of content returned (resources, conversations, shared pages that changed), which goes slightly beyond the annotation. No contradiction.

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?

The description is a single concise sentence that front-loads the key action and resource types. No wasted words.

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 no parameters, an output schema present, and a read-only annotation, the description is sufficient for an agent to know it's a safe, non-parameterized browse operation. It doesn't detail the output format, but the output schema likely covers that, and the complexity is low.

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 has zero parameters, so the description's job is minimal. The description clarifies the scope of what's browsed, which is useful since there's no schema to provide detail. No need to compensate for parameter documentation.

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 states a specific verb ('Browse') and resource ('useful resources, conversations and shared pages'), which is clear about what it does. It doesn't explicitly distinguish from siblings like 'read_updates' or 'catch_up', but the resource list is specific enough to be distinct.

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 description implies its use case (discovering changed/curated content) but doesn't explicitly say when to use it versus alternatives like 'catch_up' or 'read_updates'. There's no exclusion or comparison, but the context is reasonably clear.

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