snapshots_get_custom_snapshots

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is known. The description adds the token scope constraint, which is useful contextual information beyond annotations, though it does not disclose return format, pagination, or other behavioral traits. This is a modest addition, consistent with a 3.

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 is concise and front-loaded with the main action, followed by a key prerequisite. It contains no waste, though it may be too terse if more detail were warranted.

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 only one parameter and no output schema, the description carries the burden of explaining the tool's scope. It provides a token requirement but does not explain what a custom snapshot is, what data it returns, or how it relates to sibling snapshot tools. This leaves the agent under-informed for selection and invocation.

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 100% for the single parameter companyId, which is described as 'Company Id'. The description does not add any extra meaning or context for the parameter, so the baseline of 3 applies.

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 states the verb 'Get' and resource 'Snapshots', but it does not mention 'custom' or clarify what distinguishes this from sibling snapshot tools like snapshots_get_latest_snapshot_push or snapshots_get_snapshot_push. It is not a tautology but is generic and lacks differentiation.

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 notes a token requirement ('agency-level token, not a location PIT'), which is a prerequisite, but does not provide any guidance on when to use this tool versus alternatives. No mention of context or exclusions.

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