execution_log

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

Annotations are absent, so description must convey behavioral traits. It only states 'Get' (read-only) and the option to include archives. No mention of idempotency, access control, rate limits, or potential performance impact of large logs. Minimal disclosure.

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 extremely concise—one sentence fragment conveying core purpose. It is front-loaded and avoids fluff. However, it could be slightly more structured without adding length.

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?

Without an output schema, the description should explain return format or structure. It does not. Additionally, it lacks behavior details (e.g., ordering, default limit). Given the tool's simplicity, more context is needed for proper usage.

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 50% (only include_archives has schema description). The tool description adds explanation for 'limit' (last N entries) and clarifies 'include_archives' (optionally), though the latter is redundant. It provides adequate but not exceptional value 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?

Description clearly states verb 'Get' and resource 'execution log' with options. It provides a general sense of the tool's purpose, though it could be more specific about the log context (e.g., system vs. process). It partially distinguishes from sibling 'list_archives' by focusing on logs.

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?

No explicit guidance on when to use this tool vs alternatives (e.g., list_archives for archive files). No context about prerequisites or scenarios. The description implies basic usage but fails to set usage boundaries.

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