ghl_snapshot_get_pushes_between_dates

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

The description adds value beyond annotations by specifying the token requirement (Agency-Access-Only) and noting that 'from'/'to'/'lastDoc' are required despite generic names. It also provides the endpoint and version header. Annotations already include readOnlyHint and idempotentHint, so the description complements them with authorization context.

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 moderately concise but contains redundant phrasing (e.g., the title sentence repeated). It front-loads the critical token requirement in all caps, which is good, but could be streamlined. The structure is acceptable but not optimized for quick scanning.

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 absence of an output schema and 6 parameters (5 required), the description lacks explanation of the response format, error handling, or detailed pagination mechanics. It states 'Pagination params: limit — pass them to page through full result sets' but does not describe the structure of the returned list or cursor usage, leaving the agent with incomplete context.

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 67% (4 of 6 parameters have descriptions). The description adds marginal value by reiterating that 'from'/'to'/'lastDoc' are required query params and mentioning pagination via 'limit'. However, it does not explain 'companyId' or 'snapshotId' beyond the schema, and the schema already provides examples and format for most parameters.

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's action: 'Get list of sub-accounts snapshot pushed in time period', with a specific verb ('Get') and resource ('sub-accounts snapshot pushed in time period'). It distinguishes from siblings like 'ghl_snapshot_get_latest_push' and 'ghl_snapshot_list' by emphasizing the date range aspect.

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 mentions the agency-level token requirement and that 'from'/'to'/'lastDoc' are required query params, implying usage for date-range queries. However, it does not explicitly state when to use this tool versus alternatives like 'ghl_snapshot_get_latest_push' or 'ghl_snapshot_list', nor does it provide when-not-to-use guidance.

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