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

Annotations already declare read-only, idempotent, non-destructive, closed-world, so safety is covered. The description adds real value on top: a hard id-provenance contract (only returned member ids are valid) and a prompt-injection caveat about treating CRM field values as data, not instructions.

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?

Front-loaded with the scope in the first clause, followed by the id contract and a short security note. Every sentence earns its place; the untrusted-content warning is slightly tangential to a listing tool but is a defensible safety addition.

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, yet the description does indicate what is returned (active members eligible to own records or receive activities), which is the key unknown. It could say more about the shape/fields of a returned member, but nothing essential for correct invocation 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?

Schema description coverage is 100%, so the single workspaceId parameter is already fully documented in the schema, including the multi-workspace requirement. The description adds no syntax or format detail beyond that, so the baseline 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?

States a specific verb and resource plus a meaningful scope: 'active workspace members who can own records or be assigned activities.' It is clear what comes back, but it never distinguishes itself from the very close sibling list_members, leaving the agent to guess which listing tool to call.

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?

Gives concrete downstream guidance: use a returned member id for assign_record_owner, assign_activity, create_task and create_activity, and never invent an id or pass a user id. That constrains usage well, but there is no explicit when-to-use-this-vs-list_members statement.

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