self_augment_lesson

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

Annotations declare readOnlyHint=false, idempotentHint=false, and openWorldHint=false, and the description's 'store' is consistent with a local write. However, it does not disclose the non-idempotency consequence the schema implies (default state_key includes a timestamp, so repeated calls accumulate new records) nor whether writes are append-only or pruned later. Useful but modest value beyond 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?

A single front-loaded sentence with no filler or repetition. Slight deduction because 'Reflexion-style' is unexplained jargon that adds length without adding decision-relevant meaning for an agent.

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 6-parameter write tool with no output schema, the definition says nothing about what comes back (a state key, an acknowledgement) or how the caller should reference the stored lesson later. Annotations cover safety but not the write's observable outcome, leaving a moderate gap.

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%, so all six parameters including defaults and severity are already documented in the schema. The description adds no format, valid-value, or interplay guidance beyond the schema, 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?

Names a specific verb and resource: store a Reflexion-style self-augmentation lesson into issueops state, with the stated goal of cross-session durability. That is far clearer than the sibling 'self_augment', but the description never draws the line between this and 'self_augment' or 'state_write', so an agent must infer the distinction.

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 phrase 'for durable cross-session learning' hints at a persistence purpose but gives no when-to-use trigger, no when-not-to-use, and no named alternative. With siblings like self_augment, state_write, and loop_record_attempt in the namespace, the absence of routing guidance is a real gap.

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