list_flow_execution_contact

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

The description adds context beyond annotations by stating the HTTP method ('GET'), endpoint path, and that it 'Makes no changes' to the account. This reinforces the read-only and idempotent hints from annotations. No contradictions. However, it does not detail pagination or result structure.

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 short (5 lines) but contains repetition: 'List Flow Execution Contacts' appears twice. It is not overly verbose, but the redundancy reduces conciseness. Structure is acceptable.

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 14 parameters, no output schema, and a list operation, the description lacks details on pagination, filtering behavior, and what the response contains. This is insufficient for a complex tool; more context is needed.

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?

Input schema has 14 parameters with 79% description coverage. The tool description does not add any parameter-specific information beyond what is already in the schema. Given high coverage, baseline score of 3 is appropriate.

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 states 'List Flow Execution Contacts' and 'Fetches data. Makes no changes.' It clearly identifies the tool as a read-only list operation. However, it does not explicitly distinguish from sibling 'get_flow_execution_contact' (singular) which likely retrieves a single item. The purpose is clear but lacks explicit sibling differentiation.

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 no guidance on when to use this tool versus alternatives (e.g., 'get_flow_execution_contact'). No when-to-use, when-not-to-use, or prerequisites are mentioned. The read-only nature is already captured by annotations.

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