remote_session_errors

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It reveals that the tool searches for specific keywords, but it does not state whether the operation is read-only, what the return format looks like, or how it behaves if sessionId is omitted. This leaves significant behavioral ambiguity.

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 a single sentence that is front-loaded with the purpose and includes a useful parenthetical clarification. Every word serves a purpose, with no redundancy or filler.

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 low complexity with two optional parameters and no output schema, the description is adequate but incomplete. It does not explain what the tool returns, whether it searches all sessions when sessionId is omitted, or any output structure. More context is needed for an agent to fully understand the tool's behavior.

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 100% for both parameters (limit and sessionId), so the baseline is 3. The description adds no extra meaning about the parameters; it only mentions 'session history' which is already implied by the tool name.

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 the verb 'Find' and the resource 'error messages in session history', and the parenthetical '(looks for 'error', 'failed', 'denied', etc.)' provides specific detail. This distinguishes it from sibling tools like remote_session_history or remote_session_search by narrowing the scope to error-related content.

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 implies usage: when you need to find errors in session history. However, it does not explicitly mention when to use this tool over alternatives like remote_session_search or remote_session_history, nor does it provide exclusions or conditions for choosing this tool.

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