fonzip_membership_dues

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

Annotations already declare readOnlyHint=false and destructiveHint=true, and the description's 'silme' (delete) matches the destructive nature. The description adds an inventory of mutating operations but does not disclose side effects such as send_mail, add_payment, or the remove/activate action behavior. No contradiction with 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 a single concise sentence with no fluff, and it front-loads the domain. However, it compresses many distinct operations into one comma-separated list without grouping by operation flow or naming the action selector, which weakens its structural usefulness for a 40-parameter tool.

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 multi-operation tool with 40 parameters and no output schema, the description is far too thin. It does not explain how to select or route between operations like list, create_debt, delete, or update_debt_status, nor what return values to expect. The rich schema partially compensates, but the high-level description leaves critical invocation context missing.

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%, and each parameter already includes operation tags and enum explanations. The description itself adds no parameter-level meaning beyond the schema, so the baseline of 3 applies.

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 the resource ('Aidatlar ve borclar') and enumerates concrete operations: listing/detailing/deleting subscriptions and creating/updating/status-changing/deleting debts. It distinguishes the tool's domain from siblings like fonzip_donations and fonzip_monthly_donations, though it is a packed summary rather than a structured operation list.

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 provides clear domain context with 'Aidatlar ve borclar', implying this tool is for membership dues and debt operations. However, it gives no explicit when-to-use guidance, exclusions, prerequisites, or comparison against sibling tools, leaving usage mostly to inference.

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