list_all_contact_automations

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is clear. The description adds 'Fetches data. Makes no changes' which reinforces but does not expand beyond annotations. No information about rate limits, authentication, or response structure is provided.

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 concise (3 short lines) and front-loaded with the READ-ONLY indicator and endpoint. Every sentence serves a purpose, though it could include more detail without becoming verbose.

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?

Despite detailed annotations and complete schema coverage, the description lacks critical context: it does not explain how to specify a contact, how pagination works despite limit/offset parameters, or what data is returned (no output schema). The tool's relationship to similar siblings is also unclear.

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 input schema covers all 4 parameters with descriptions, so schema coverage is 100%. The description does not add any additional meaning or usage context for the parameters (e.g., how filters or orders apply to contact automations). Baselined at 3 due to complete schema coverage.

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 all automations a contact is in' which is a specific verb-resource pair. However, it does not clarify how to specify which contact (the input schema lacks a contact ID parameter), and the tool name is ambiguous between listing all contact automations globally vs. for a specific contact. The sibling tool 'list_all_contactautomations_for_contact' suggests a more targeted alternative, increasing confusion.

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?

No explicit guidance on when to use this tool versus alternatives like 'list_all_contactautomations_for_contact' or 'list_all_automations'. The description provides no context about use cases, prerequisites, or scenarios where this tool is appropriate.

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