get_log

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

Discloses ordering (newest first), content (what was added when, reasoning), and default behavior (small window). No annotations provided, so description carries burden fully. Lacks mention of potential for pagination or performance.

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 clear, concise sentences for purpose, followed by clean argument list. No fluff, every sentence adds value.

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?

Output schema exists, so not required to describe return shape. Covers essential context: ordering, reasoning, default limit. Minor gap: no mention of error handling or empty results.

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 coverage is 0%, but description fully explains both parameters: since as ISO date filter and limit as max entries with default small window, adding critical context missing from 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?

Clearly states it returns the wiki's change log, newest first, and distinguishes from sibling get_index by contrasting 'what the wiki holds' vs 'how it got there'.

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?

Contrasts with get_index to guide selection, mentions optional since and limit arguments, and notes default small window for logs. Could be more explicit about when not to use.

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