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

readOnlyHint=true already declares this as a safe read, so the description owes only supplementary context. It adds nothing about pagination behavior, filter semantics, or result scope — just a restatement of the HTTP endpoint, which does not help an agent decide or call correctly.

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, front-loaded with the purpose and no filler. Efficient, though the second sentence is low-value API trivia.

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?

For a 5-parameter filtered-list tool with no output schema and an undocumented pair of filter arrays, the description says far too little. An agent cannot tell what customer_ids/membership_ids do or how results are paginated.

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 60%: page_size, company_id, and page_token are documented, but customer_ids and membership_ids have no description at all. The description does not explain these filter arrays, so the coverage gap is unmitigated.

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 ('customer membership subscriptions'), so the operation is clear. It does not distinguish itself from the sibling moego_list_memberships, leaving the agent to infer what a 'subscription' is versus a plain membership.

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 gives no when-to-use guidance, no prerequisites, and never mentions the closely related moego_list_memberships sibling as an alternative. The agent gets no routing signal beyond the resource name.

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