security_proxy_parse

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

No annotations. Description mentions 'real-time analysis' implying network activity, but does not disclose side effects, required permissions, or whether it modifies anything.

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?

Fairly concise but includes irrelevant 'Menu ID' and a redundant referral to describe_tool, which could be omitted.

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?

No output schema, no parameter descriptions, and the description fails to explain what the tool returns or how results are structured. Very incomplete for a tool with nested options.

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 0% and description provides no information about the two required parameters (proxies string format or options object contents).

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 states it tests proxies with analysis, but does not clearly differentiate from sibling tools like security_proxy_test, nor does it explain the 'parse' aspect of the name.

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 on when to use this tool versus alternatives, no when-not or prerequisites mentioned. Only states supported proxy types.

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