Show recommendations

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds one useful behavioral fact beyond that: only the most recent saved snapshot is returned, not history or all versions. It says nothing about what happens when nothing has been saved, or what the output contains.

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; every word earns its place. It is arguably too sparse for the amount of ambiguity left, but that is a completeness issue rather than verbosity.

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 tool is simple (0 params, no nesting), so little is required, but there is no output schema and the description never explains what a 'recommendation' record looks like or how an empty state is signalled. For a read tool whose whole value is its return payload, that is a real 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?

There are zero parameters, so the baseline is 4. 'Last saved' also conveys the implicit selection behavior (no filtering, no date range, no identifier), which is meaningful given the empty schema.

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?

"Show the last saved recommendations" gives a clear verb (show) and resource (recommendations) with a scope qualifier (last saved). An agent can distinguish it from save_recommendations by the verb, but the description never explicitly names that sibling or clarifies what 'recommendations' are in this domain.

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 'last saved' weakly implies a prior save_recommendations call must have happened, but there is no explicit when-to-use, when-not-to-use, or alternative named. With siblings like get_evidence and show_profile in the set, the agent gets no routing help.

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