keil_get_session_log

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

No annotations are supplied, so the description carries the full burden, and it does disclose two useful traits: the record count is bounded at 1..500 and a durable JSONL log path is returned alongside the records. It does not state whether the call is read-only, how records are ordered, or what happens when fewer records exist than requested, leaving gaps for a no-annotation tool.

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; the retrieval target and the returned log path are stated immediately. Nothing in the sentence is redundant.

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?

An output schema exists, so the description need not explain return values, and the record cap and JSONL path hint are appropriately included. However, for a log-retrieval tool with an undocumented parameter, the description should still clarify what 'tail' counts and when this log is preferable to the build log or last-error siblings.

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 lone 'tail' parameter with default 50 is undocumented in structured fields. The description's '1..500' bound implicitly conveys the valid range and default behavior of that tail count, but it never names the parameter, states the default, or explains whether tail means most-recent-N records or log lines.

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 uses a specific verb and resource: 'Return the most recent ... operation records and durable JSONL log path.' That tells an agent it retrieves a session/operation log plus the on-disk JSONL path, which is distinguishable from siblings such as keil_get_build_log or keil_get_last_error by name. It does not explicitly contrast itself with those siblings, keeping it below a 5.

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 gives no guidance on when to use this tool rather than keil_get_build_log, keil_get_last_error, or keil_get_status, and it names no alternatives or exclusions. An agent must infer from the name alone that this is the general session-history tool.

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