get_snapshot

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the core safety profile is covered. The description adds no behavioral nuance beyond the listed return content; it does not mention pagination, size, permissions, or error behavior, but it also does not contradict the annotations.

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, compact sentence that front-loads the operation and resource, then lists the relevant content areas. There is no filler or redundancy.

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?

For a one-parameter read-only retrieval tool without an output schema, the description gives a useful overview of the return content (agent state, schemas, triggers, MCP servers). It is complete enough for correct selection and invocation, though it does not fully specify the response structure or edge-case behavior.

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 100% and the single parameter snapshot_id already has a clear UUID description. The description adds that the snapshot is a 'publication snapshot', which gives useful context, but otherwise does not add meaning beyond what the schema already provides. Baseline 3 is appropriate.

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 a specific action ('Retorna') and a clear resource ('detalhes completos de um snapshot de publicação') and enumerates meaningful content categories (agent state, schemas, triggers, MCP servers). This distinguishes it from list-style siblings like list_snapshots and from mutation tools like rollback_snapshot.

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 this tool should be used when a complete snapshot's details are needed, and the verb 'Retorna' suggests a read/retrieval operation. However, it does not explicitly state when to prefer this over alternatives such as list_snapshots or get_version, nor does it provide any 'not for X' guidance.

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