ghl_snapshot_list

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true. The description adds context about agency-level authentication and the scope of snapshots (own and imported), but does not disclose additional behavioral traits like pagination or rate limits.

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 three sentences, but includes technical endpoint details (URL, version header) that are likely unnecessary for an AI agent. The important constraint (agency token) is front-loaded.

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?

The description does not explain return values, pagination, or what 'own and imported' means in practice. Given no output schema, the agent lacks information about the response structure. However, for a simple list operation, it is minimally adequate.

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?

The input schema has 100% description coverage for its single parameter (companyId), so the baseline is 3. The description does not add any further meaning to the parameter beyond what the schema provides.

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 list of all own and imported Snapshots, distinguishing it from other snapshot operations like creating share links or getting push history. The verb 'Get' and resource 'Snapshots' are explicit, and the agency-level token requirement further clarifies scope.

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 explicitly mandates an agency-level token (Agency-Access-Only), guiding the agent on when this tool is applicable. It does not explicitly state when not to use or name alternatives, but the token constraint effectively differentiates from location-scoped tools.

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