xr18_snapshot_set_scope

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

There are no annotations, so the description must fully convey behavioral impact. It only says it sets a value, which implies a write/mutation operation, but it gives no detail on what recall-scope affects, whether the change persists, error behavior, or whether the slot and scope pair have constraints beyond the stated range.

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, front-loaded sentence that communicates the core action and a key constraint with no wasted words. It is appropriately sized for a simple two-integer-parameter command.

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?

Given the lack of annotations, output schema, and schema-level parameter descriptions, the definition is too thin. It fails to explain the role of the slot parameter, the practical meaning of recall-scope, or any expected behavior/return value, so an agent cannot fully predict the tool's 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 description coverage is 0%, so the description must compensate for both parameters. It adds meaning for the scope value by giving a range, but it never explains what 'slot' refers to or how slot and scope relate, leaving one required parameter entirely undefined.

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 uses a specific verb (Set) and resource (snapshot recall-scope index) and adds an exact range (0 through 59), making the tool's purpose unambiguous. This clearly distinguishes it from sibling tools like xr18_snapshot_set_name or xr18_snapshot_load, even without explicit comparisons.

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 intended use is implied by the explicit action statement: if an agent needs to set a snapshot recall-scope, this is the tool. However, it does not state when to prefer this over alternatives or describe any prerequisites or exclusions, so guidance is only at an implicit level.

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