ghl_snapshot_get_latest_push

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false. The description adds beyond that by specifying the required agency-level token, the HTTP method (GET), and the exact endpoint path, which enhances behavioral transparency.

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 concise with four short lines. It front-loads the important security note and then states the purpose. Minor redundancy ('Get Last Snapshot Push' appears twice) but overall efficient.

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?

With no output schema, the description should describe the return value (status). It only says 'get status' without details. Parameters are also unexplained. The tool's safety profile is covered by annotations, but context on behavior and results is lacking.

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 0% and the description does not explain any parameter. Although snapshotId and locationId appear in the endpoint string, companyId is not mentioned, and none are defined meaningfully. This fails to add value.

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 the latest snapshot push status for a location, using the verb 'Get' and specifying the resource. It distinguishes from sibling tools like ghl_snapshot_create_share_link and ghl_snapshot_list by focusing on the latest push.

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 usage for obtaining the latest push status but lacks explicit guidance on when to use this tool versus alternatives like ghl_snapshot_get_pushes_between_dates. The token requirement is a prerequisite, not a usage guideline.

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