iyke_logs

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

No annotations are provided, so the description carries the burden. It discloses the tool reads logs and includes error captures, and mentions a limit of 500 entries. However, it does not specify if the logs are persistent or session-bound, nor does it describe the output format. There is no contradiction with annotations.

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, concise sentence that conveys the core functionality and key constraints (last 500, includes error types). Every word earns its place with no unnecessary information.

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 tool is a read operation with no output schema and no annotations, the description provides reasonable context: it reads recent logs, includes errors, and has a limit. However, it omits details about the output format, whether logs are cumulative or reset, and the behavior of optional filters.

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 provides descriptions for two of three parameters (since and source). The description does not add additional meaning to any parameter; for example, it does not explain how the 'level' filter works. With 67% schema coverage, the description adds marginal 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?

The description clearly states the tool reads recent console and error logs from the running webview, including specific error captures. It uses a specific verb and resource, and while it doesn't explicitly differentiate from siblings, the tool name and description make its purpose obvious.

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 for reading logs but provides no explicit guidance on when to use this tool versus alternatives. No alternative tools are mentioned, and there is no discussion of prerequisites or when not to use it.

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