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

The annotations already declare the tool as read-only, idempotent, and non-destructive. The description adds valuable behavioral detail by stating that every call re-verifies workspace/account/token binding and refreshes tokens when needed, which is not fully covered by the annotation hints. No contradiction exists between the description and annotations.

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 two sentences, but each sentence is substantive. The first sentence concisely scopes the operations by category, and the second adds behavioral detail about auth verification and token refresh. No redundant or filler content is present.

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 description provides enough context for a multi-action gateway, especially given the rich schema and annotations. It covers the important auth behavior and the breadth of operations; the lack of a detailed output description is mitigated because the schema's pagination_token field already explains how to handle response cursors.

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 100%, so every parameter is already well-documented in the input schema. The description does not add additional parameter-level meaning, which keeps the score at the baseline expected for a fully documented schema.

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 identifies a specific resource and operation class: a verified X read/search gateway, listing the covered content types such as posts, recent search, full-archive search, mentions, users, followers/following, and DM events. It is clear and detailed, though it does not explicitly distinguish itself from sibling tools like invoke_get_post and invoke_list_posts, which may be relevant to the same read actions.

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 the appropriate context: use this tool for authenticated X read/search operations, and it calls out that it verifies workspace/account/token bindings on every call. However, it gives no explicit guidance about when to prefer this gateway over sibling tools or when not to use it, so the usage context is mostly implied.

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