aa_list_recent_updates

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

With no annotations provided, the description carries the full burden. It discloses the baseline snapshot creation on first run, the option to preview without saving, and the return format (structured diff). It does not cover potential side effects like disk usage or if the snapshot is stored persistently, but overall it provides sufficient behavioral context.

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 well-structured with a clear overview paragraph followed by Args/Returns sections. It is informative without extraneous details. Minor improvement could be shortening the first sentence, but it's effective.

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 output schema is present but not shown in the context; however, the description covers return value structure ('JSON with structured diff'). The single parameter is fully explained. No gaps noted for a tool of this complexity.

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 add meaning. For the only parameter (save_new_snapshot), the description clearly explains its effect: saving after diffing vs preview-only. This goes well beyond the schema's default and type, fully compensating for the lack of schema descriptions.

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 ('Detect') and resource ('LLM model changes by comparing current data to the last local snapshot'). It distinguishes from siblings like aa_compare_models (which compares specific models) and aa_list_llms (which lists all models) by focusing on change detection over time.

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 explains the initial snapshot behavior and preview mode via save_new_snapshot, giving implicit usage context. However, it does not explicitly state when to use this tool versus alternatives (e.g., aa_compare_models, aa_list_llms), nor does it mention prerequisites or clear 'when not to use' cases.

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