get_cleaning_history

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

Describes the outputs (total space freed, number of sessions, details) but does not disclose any behavioral traits like whether it requires specific permissions, if it is destructive, or if results are cached. Without annotations, the description could be more transparent.

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?

Two concise sentences that convey the core purpose and provide a usage example. No unnecessary words, though the second sentence could be more specific about the output format.

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 simple functionality, one optional parameter, and no output schema, the description is sufficiently complete. It covers what the tool returns and a typical use case.

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?

Only one parameter 'limit' with schema description covering 100%. The description does not add extra meaning beyond the schema, so baseline score of 3 is appropriate.

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?

Clear statement of what the tool does: retrieving history of cleaning sessions with specific outputs (space freed, number of sessions, details). The example query provides context, but it doesn't explicitly differentiate from the sibling 'show_cleaning_history', which may be similar.

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?

Provides a concrete use case ('answer 'how much did I clean last week?''), which helps an agent decide when to use it. However, no guidance on when not to use or alternatives.

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