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

With readOnlyHint=true already declared, the description adds useful behavioral context beyond annotations: empty queries browse all pages and pagination is stable. It does not contradict annotations, and this extra context helps an agent predict behavior and plan paginated calls.

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?

Two sentences, front-loaded with the core purpose, and every phrase earns its place. The mention of stable pagination is meaningful and compact.

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?

The presence of an output schema reduces the need to describe return values, and the readOnly annotation covers safety. However, the description is incomplete for a 4-parameter tool because it leaves source and limit unexplained and fails to distinguish this tool from its closest siblings.

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%, so the description must compensate, but it only alludes to q via the empty-query behavior and to cursor via stable pagination. It does not explain limit or source, and provides no semantics for any parameter by name.

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 clearly states the tool finds communal pages and their discussions, which is a specific enough verb-resource pairing. It does not explicitly differentiate from sibling tools like browse_frontpage or search_workspace, but the reference to 'communal pages' and 'discussions' gives reasonable scope.

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 empty-query browsing behavior gives some usage context and implies a good default invocation, but the description never says when to choose search_pages over browse_frontpage or search_workspace, and offers no exclusions or alternatives. Usage guidance is implied rather than explicit.

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