get_latest_info

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

No annotations are present. The description states 'tails the newest info log file,' which implies a non-destructive read operation, but it does not disclose whether any side effects, authentication requirements, or rate limits exist. For a log retrieval tool, this is minimally adequate.

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 two sentences, but the second is a fragment ('Tails the newest info log file.'). It is fairly concise, though the information could be combined into one clear sentence without losing meaning.

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 no output schema and simple parameters, the description covers the essential behavior: retrieving latest Info logs by tailing from a specific date. It omits details about the return format but is likely sufficient for a straightforward log retrieval tool.

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?

The input schema has 100% coverage with descriptions for both parameters. The description adds only that the tool 'tails' the log file, which is already implied by the 'trailing lines' term in the schema. Thus, the description provides little additive meaning beyond the 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?

The description clearly states 'Retrieve the latest Info logs from the active appserver' and 'Tails the newest info log file', specifying the log level and source. This distinguishes it from sibling tools like get_latest_error, get_latest_warn, and get_latest_debug which handle different log levels.

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?

Usage is implied by the name and description (for Info-level logs), but there is no explicit guidance on when to use this tool versus alternatives. No exclusions or context-specific advice are provided.

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