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

Annotations cover the safety profile (readOnlyHint=true), and the description adds real behavioral context beyond them: it is cursor-paginated and returns participants and read status. It stops short of noting auth or rate-limit behavior, so not a 5.

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?

Three short sentences, front-loaded with purpose then parameter selection then pagination and endpoint. Efficient, with only minor abbreviation (

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 read-only listing tool with no output schema, the description covers what is returned (participants, read status), how scoping works, and pagination. Adequate for correct invocation; only the sibling disambiguation is 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?

With 75% schema coverage the baseline is 3, but the description adds value: it clarifies the lead_uid/agency_uid alternative and notes the agency default, which shapes how the otherwise-undocumented lead_uid is used. Cursor behavior is also reinforced.

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 guest-messaging threads) plus scope (agency or one lead) and the return content (participants and read status). It does not explicitly differentiate itself from the sibling hostfully_list_messages, which is the main gap.

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?

"Give lead_uid, or agency_uid (or the default)" gives clear guidance on which parameters select which scope, but there is no guidance on when to use this thread-listing tool versus hostfully_list_messages or hostfully_search_leads. Usage is only implied relative to tool selection.

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