list_all_contactautomations_for_contact

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

Annotations already provide readOnlyHint, openWorldHint, idempotentHint, destructiveHint. Description adds the HTTP method and path, reinforcing read-only behavior. No contradictions, but does not discuss pagination or rate limits beyond the schema.

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?

Description is extremely concise: a compact emoji-and-URL summary, a clear purpose statement, and a safety note. Every line adds value with no redundancy.

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 simple list tool, the description combined with the input schema covers functionality and parameters. Missing output schema is not critical here, but the return format is not described. Still sufficiently complete for a straightforward read operation.

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 100% coverage with descriptions for all 5 parameters. The tool description does not add additional meaning beyond what the schema already provides, so baseline of 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?

Description states 'List all automations the contact is in', clearly identifying the action (list) and resource (automations for a contact). The inclusion of HTTP method and path adds clarity and distinguishes from sibling tools like list_all_automations.

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?

Description notes that it 'Fetches data. Makes no changes,' implying safe usage, but lacks explicit guidance on when to use this tool versus alternatives like retrieve_contact_automation_entry_counts. Usage is implied by name but not spelled out.

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