pbs_snapshot_protected_get

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

Without annotations, the description carries full burden. It declares the tool READ-ONLY upfront, discloses the return type discrepancy ('endpoint declares null but returns a boolean'), and mentions required configuration. This fully informs the agent of behavioral traits.

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 compact and front-loaded with the key characteristic 'READ-ONLY'. Every sentence adds value with no repetition or fluff. It efficiently conveys purpose, sibling relationship, nuance about return type, and config requirement.

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 covers purpose, sibling existence, return type nuance, and config requirement. It does not explicitly handle error cases or missing snapshot behavior, but given the presence of an output schema and the tool's simplicity, this is 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?

Schema coverage is 100%, so baseline is 3. The description does not add extra meaning beyond the schema descriptions for the parameters. No additional constraints or formats are provided.

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 verb 'query' and the resource 'protection flag for a specific backup snapshot'. It explicitly distinguishes itself as 'the READ half of the shipped pbs_snapshot_protected_set', leaving no ambiguity about its purpose versus its sibling.

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 when to use this tool (to query protection flag) and pairs it with its set counterpart, but does not explicitly state when not to use or provide alternative tools. The prerequisite 'Needs PROXIMO_PBS_* config' gives context.

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