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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real context (OAuth flow through the host, explicit 'Never creates knowledge'), but does not describe pagination behavior despite the cursor param, nor what 'connect' changes in the environment.

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 short sentences, action-leading and with the safety disclaimer front-loaded in the second sentence. No filler, though the phrasing 'Connect or grant knowledge read permission' is slightly redundant.

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?

Output schema exists, so return values need not be explained, but the definition omits usage routing and any parameter guidance for a tool with 0% schema coverage. Adequate but with clear gaps for a dual auth-plus-list operation.

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 both params, so the description carries the full burden, yet it only vaguely implies paging ('a page of ... topic labels') and says nothing about the locale parameter or cursor format. It leaves the agent guessing at the two parameters it must supply.

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 compound action (connect/grant read permission via host OAuth) and a concrete resource (the authenticated owner's topic labels), so the agent knows it does both auth and listing. It is clear on its own, though it does not explicitly distinguish itself from siblings like check_memostem_connection or start_memostem.

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 when-to-use/when-not guidance and no reference to any alternative. An agent cannot tell from the description whether this precedes start_memostem or check_memostem_connection, or what condition should route it here.

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