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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds genuinely non-obvious behavior: results can include workspaces with locked_by_plan: true that are unusable until upgrade or dashboard action. It doesn't cover pagination limits or the return shape, keeping it below a 5.

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 tight sentences with the core purpose front-loaded and no filler. The parenthetical '(accounts, posts)' is slightly awkward but earns its place by naming affected resources.

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?

A paginated list tool with no output schema should at least hint at bounds or ordering, which it doesn't. The locked-plan disclosure is valuable, but the pagination parameters and result shape remain unexplained, leaving an agent guessing on page/limit behavior.

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 coverage is only 33% — page and limit have no descriptions at all, and the description says nothing about pagination or filtering semantics. With low coverage the description should compensate, but it does not; only 'search' is self-documenting in the 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?

States a specific verb ('List') and resource ('authenticated user's Feedlio workspaces') with clear ownership scope. It is distinguishable from siblings like list_posts or list_social_accounts by resource, though it doesn't explicitly say so.

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 guidance on when to call this versus related tools (e.g., before create_workspace or set_default_workspace), nor any prerequisites. The second sentence explains plan-locked behavior but is not usage selection guidance.

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