Create membership

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

No annotations provided, so description carries full burden. It discloses auto-calculation of dates and the required environment variable. However, it does not mention side effects, error scenarios, or whether the operation is idempotent.

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 sentences, front-loaded with key information, no wasted words. Efficient and clear.

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?

No output schema, 8 parameters including a nested object. Description omits return value, error handling, and details on the 'extra' parameter. For a creation tool, the agent lacks information on what happens after success.

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 63%. The description adds no new parameter-specific information beyond what the schema already provides (e.g., auto-calculation is a behavior, not parameter semantics). Since coverage is moderate but not low, baseline score of 3 is appropriate.

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?

Description clearly states 'Create a Membership record for a contact'. It specifies the resource (membership) and action (create), and adds a specific behavioral detail about auto-calculation of dates. This distinguishes it from sibling tools like civicrm_create_contact.

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?

Description mentions a prerequisite (CIVICRM_ALLOW_WRITES=true) but does not explicitly compare to alternatives or provide when-not-to-use guidance. It implies usage for creating memberships, but lacks context on when to prefer this over other tools like civicrm_update_contact.

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