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

Goes well beyond the annotations (readOnly=false, destructive=false, idempotent=false): it discloses partial-update semantics ('only sent fields change'), that price changes affect only new buyers while current members keep their price, that the free tier is never priced, and the full Stripe payout/hold behavior with no separate community Stripe. This is rich behavioral context an agent cannot get from the structured fields.

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 create/edit distinction is front-loaded and each sentence carries information, but the single dense paragraph with many em-dash clauses is long and the Stripe/payout detail, while useful, could be tightened or deferred.

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 an 8-param mutation tool with no output schema, the description covers behavior, permissions, pricing rules, and the payment flow well. Gaps remain: community_id semantics, what fields are required when creating, and error/validation behavior are not addressed.

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?

With 0% schema description coverage, the description carries the burden and mostly succeeds: tier_id's create/edit/'free' semantics, privileges capped at 12, and monthly/yearly_cents defined as USD with a 100 minimum. However, community_id is never explained and create-mode requiredness of name is left implicit.

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+resource ('Create ... or edit ... a paid membership tier of a community you run') and immediately disambiguates the two modes via the omit/pass tier_id convention. It is clearly distinguishable from siblings like list_membership_tiers, archive_membership_tier, and unarchive_membership_tier.

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?

Gives explicit mode-selection guidance ('omit tier_id' to create, 'pass tier_id' to edit) plus the special case of tier_id='free' and the auth constraint ('Creator or admin only'). It stops short of naming sibling tools (e.g., list_membership_tiers to discover tier_id), so it is strong context without full alternative routing.

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