list_contacts_for_date_range

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It reveals the date format (YYYY-MM-DD) but does not mention whether the operation is read-only, pagination behavior, sorting, or error handling. This is insufficient for a list endpoint.

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 a single sentence that front-loads the core purpose. No extraneous words or repetition.

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 has 3 parameters (2 required) and an output schema (not provided), the description lacks explanation of pagination (top parameter) and return value structure. While adequate for a simple filtered list, it falls short of completeness considering the sibling context and schema coverage.

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 description coverage is 0%, so the description must compensate. It specifies the date format for start_date and end_date but does not describe the 'top' parameter, leaving its purpose (likely pagination) unclear. The description adds only partial meaning beyond the schema.

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 the tool lists contacts filtered by a date range, using the specific verb 'List' and resource 'contacts created within a date range'. This distinguishes it from sibling tools like list_contacts (which likely lists all contacts) by specifying the date filter.

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 implies the tool is for listing contacts created in a date range but does not explicitly state when to prefer it over alternatives like list_contacts or other filtered list tools. No when-not or alternative mentions.

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