retrieve_contact_data

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds that it is a GET request and does not change the account, but this is minimal. No additional behavioral information such as rate limits, permission requirements, 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 short (4 sentences) but contains some redundancy: 'Retrieve a contact's data' and 'Fetches data' say the same thing. The emoji and path are useful. Structure is acceptable but could be tighter by removing duplicates.

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 5 parameters and no output schema, the description is minimal. However, annotations and schema descriptions cover the essential aspects (read-only, id required, pagination, filtering). The description does not explain the return format or how orders/filters work, but the schema parameter descriptions provide that context. Overall adequate but lacks summary of behavior.

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%, so the baseline is 3. The description does not elaborate on parameters beyond the schema's own descriptions. The first line hints at 'Contacts' but adds no new meaning to the parameters like id, limit, offset, orders, or filters.

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 clearly states it retrieves a contact's data and that it is read-only. It distinguishes itself from other retrieve tools by specifying 'contact data' and including the HTTP path. However, it does not explicitly differentiate from sibling tools like 'get_contact' or 'retrieve_contact_field_values'.

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 guidance on when to use this tool versus alternatives. It does not mention prerequisites, when to use pagination/filters, or when to prefer other retrieve tools. The description only states it fetches data without changes, which is implied by the name and annotations.

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