retrieve_a_secondary_contact

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

Annotations already provide readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds 'GET /contactDeals/{id}' and 'Fetches data. Makes no changes', which aligns with annotations. It doesn't provide deeper behavioral context beyond what annotations supply, but it does confirm the HTTP method.

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 somewhat repetitive, stating 'Retrieve a secondary contact' twice. It includes emoji and line breaks, which add visual structure but also redundancy. It could be more concise by removing duplicate phrasing.

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 is simple (one parameter, no output schema) and annotations cover safety, the description is adequate. It provides the endpoint and confirms read-only behavior. However, it does not explain the return format or error handling, but for a straightforward read operation, completeness is acceptable.

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 coverage is 100% with a single parameter 'id' described as 'Secondary Contact's id'. The description does not add any additional semantic information beyond what the schema already provides. Baseline is 3.

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 'Retrieve a secondary contact' and 'Fetches data. Makes no changes to your ActiveCampaign account.' The verb 'retrieve' and resource 'secondary contact' are specific. The context of sibling tools includes 'list_all_secondary_contacts' and mutation tools, so this tool is clearly distinguished as a single-item read.

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 does not explicitly state when to use this tool versus alternatives like 'list_all_secondary_contacts'. It only says 'Retrieve a secondary contact', which implies use when you need a specific record by ID. No exclusions or alternative guidance is provided, but the purpose is clear enough for an agent to infer basic usage.

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