get--v3-lists-list_address-members-member_address

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

With no annotations provided, the description carries the full burden of behavioral disclosure but fails completely. It doesn't indicate whether this is a read-only operation, what permissions might be required, whether it's idempotent, what error conditions exist, or what the response format looks like. The single phrase 'Get a member' reveals nothing about the tool's behavior beyond the basic action implied by the verb.

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?

The description is maximally concise at just two words. While this represents severe under-specification rather than ideal conciseness, it technically contains no wasted words and is front-loaded with the core action. Every word earns its place, even though that place is inadequate.

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?

Given the tool has 2 required parameters with 0% schema coverage, no annotations, and no output schema, the description is completely inadequate. It fails to explain what the tool does beyond the most basic level, provides no parameter guidance, no behavioral context, and no relationship to sibling tools. This leaves the agent with insufficient information to use the tool effectively.

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?

The schema has 0% description coverage for both parameters (list_address and member_address), and the description provides zero information about what these parameters mean, their expected format, or their relationship. For a tool with two required parameters and no schema documentation, this represents a critical gap in understanding how to use the tool correctly.

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?

The description 'Get a member' is a tautology that essentially restates the tool name without adding meaningful context. It doesn't specify what type of member (email list member, team member, etc.) or what resource is being retrieved. While it includes a verb ('Get'), it lacks specificity about the domain or context of the operation.

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 description provides absolutely no guidance about when to use this tool versus alternatives. It doesn't mention prerequisites, context, or relationships to sibling tools (like other list-related tools such as 'get--v3-lists-list_address-members' which likely retrieves multiple members).

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