check_page_size

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

With no annotations, the description carries the full burden. It does disclose a cost ($0.001 USDC via x402), which is a behavioral trait, but it does not explain what actions the tool performs, what output it returns, or any side effects or limitations.

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 short and lacks substantive content. While it is concise, it is under-specified; the cost note is useful but the core purpose is not explained.

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?

There is no output schema, no annotations, and a generic parameter container. The description does not explain what a 'page' is, how to invoke the tool, or what the result looks like, making it severely incomplete for an agent to use correctly.

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 only has a generic 'params' object, and the description adds no information about what parameters should be included. There is zero compensation for the lack of meaningful schema detail.

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 is essentially a restatement of the tool name ('check page size') with a category label ('Security & Network tool'). It fails to specify what 'page size' refers to (web page, memory page, etc.) and does not distinguish this tool from siblings like http_headers or check_links.

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 the many similar network/security tools. There is no mention of prerequisites, scenarios, or alternatives.

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