iyke_network

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

The description implies a read-only operation and lists returned fields. However, without annotations, it does not disclose whether the buffer is cleared on read, if data persists across sessions, or any potential side effects. Minimal but adequate for a simple read.

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 and front-loads key information, but it omits critical parameter details. It is efficient but incomplete, which reduces its overall conciseness value.

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, partial parameter coverage, and no annotations, the description falls short. It explains the output fields adequately but fails to describe the parameters, making the tool's full usage unclear.

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 two parameters (since, source) with 0% schema description coverage. The description does not mention either parameter, leaving the agent without any clue about their purpose, format, or effect on the results.

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 fetch + XHR network activity with a limit of 100 entries. The verb 'Read' and resource 'network activity' are specific, and the tool is easily distinguished from sibling tools like iyke_dom or iyke_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 guidance is provided on when to use this tool versus alternatives (e.g., iyke_devtools for broader debugging). There is no mention of prerequisites, limitations, or situations where another tool would be more appropriate.

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