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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint, so the safety profile is covered; the description's mention of "GET /api/v1/contacts/exists_in_sub_list" largely restates that it is a read. It adds the useful constraint that the check is scoped to exactly one contact and one list, but says nothing about the response shape or whether a miss is an error versus a false answer.

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 with the predicate front-loaded and zero padding. The trailing API path is mild filler but does confirm the underlying read semantics without obscuring the main clause.

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?

With three parameters and no output schema, the description should tell the agent what it gets back (a boolean or membership record) and how a non-member is represented. That return-value gap is the main missing piece; the input side is fully covered by the schema.

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 100% and each parameter already documents itself, including the email-or-member_id exclusivity. The description's "by email or member id" merely echoes the schema, adding no format or precedence guidance beyond it.

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 precise predicate and resource: whether one contact, identified by email or member id, belongs to one list. This is unmistakably distinct from the sibling mutation tools (add/remove/subscribe) that share the same list vocabulary.

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 single-contact, single-list scope implies when to use it, but there is no explicit statement of when to prefer this over robly_find_contact or robly_list_contacts, nor any prerequisite such as needing a sub_list_id from robly_list_sub_lists.

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