Session instructions (flash alias)

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

The description lists mutating actions like 'push', 'ack', and 'clear', but annotations declare readOnlyHint=true, indicating read-only operations. This is a direct contradiction. Additionally, despite destructiveHint=false, operations like 'clear' are destructive. The tool's behavioral traits are inconsistent with 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 concise, consisting of two short sentences that front-load the key fact (alias of instruct) and then list actions. Every sentence adds value, but the structure could be improved with clearer formatting.

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?

Despite the schema covering parameter details, the description lacks essential context about what the instruction cache is, how the actions work, and the relationship to the 'instruct' tool. For a tool with 9 parameters and multiple actions, this leaves significant gaps for an AI agent to understand correct usage.

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% coverage with descriptions for all 9 parameters. The description does not add any additional meaning beyond the schema, so a baseline score of 3 is appropriate. No parameter-specific elaboration is 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 states it is an alias of 'instruct' and specifies 'session-scoped instruction cache operations', listing 8 actions. This clearly identifies the tool's purpose and distinguishes it from sibling tools like 'instruct', though the exact distinction is implied rather than explicit.

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?

No guidance is provided on when to use this tool versus alternatives. While it is marked as an alias of 'instruct', there is no explanation of when to prefer 'flash' over 'instruct' or other siblings, nor any mention of prerequisites or limitations.

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