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

With readOnlyHint=true already declaring the safety profile, the description adds real behavioral context beyond annotations: the semantic meaning of memberId (converted vs open) and the underlying GET endpoint. It does not describe pagination/result-size behavior, but for a read-only list tool this is solid added context.

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 compact sentences plus a short endpoint note; the core purpose and conversion rule are front-loaded. The trailing 'Momence: GET /api/v2/host/customer-leads' is low-value for an agent but not disruptive.

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?

There is no output schema, but the description covers the key interpretive need (what 'converted' means) and how to obtain valid filter ids. Details like default page size and total counts live in the schema, so the description is largely complete for correct invocation.

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%, so the baseline is 3, and the description adds meaning beyond the schema by tying sourceId and stageId to the sibling lookup tools needed to resolve them. It also frames query as search text over name/email/phone, reinforcing rather than merely repeating the schema.

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 and resource ('List the studio's sales leads') and narrows scope with 'open and converted'. It also distinguishes the data model by defining that a non-null memberId means converted, so an agent knows exactly what population it is querying.

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?

Explains the available filter axes (search text, lead source, pipeline stage) and explicitly routes the agent to momence_list_lead_sources and momence_list_lead_stages for id resolution. It gives clear usage context but no explicit when-not-to-use or exclusion against near siblings.

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