Android Proxy MCP

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While it mentions the tool reads chunks of large content with pagination, it doesn't address important behavioral aspects like whether this operation is safe (read-only), what permissions might be required, error conditions, or what format the returned content will be in (raw bytes, decoded text, etc.).

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 with just two sentences that each earn their place. The first sentence states the core functionality, and the second sentence provides important context about when to use it. There's zero wasted language or redundancy.

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?

For a tool that reads potentially sensitive traffic data with 4 parameters and no output schema, the description is insufficient. It doesn't explain what the tool returns (content format, structure, or metadata), doesn't address authentication or permission requirements, and provides minimal guidance on error handling or edge cases despite the tool's potential complexity.

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?

With 100% schema description coverage, the input schema already documents all 4 parameters thoroughly. The description adds minimal value beyond the schema - it mentions '分页读取' (pagination reading) which relates to offset/length parameters, but doesn't provide additional semantic context about parameter interactions or usage patterns.

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's purpose with specific verbs ('分片读取' - chunked reading) and resources ('请求体或响应体' - request body or response body). It distinguishes from siblings like traffic_list (which likely lists traffic) and traffic_get_detail (which might get full details), but doesn't explicitly name these alternatives.

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 provides implied usage context ('用于查看大内容，支持分页读取' - for viewing large content, supports paginated reading), suggesting this tool should be used when dealing with large bodies that need chunked access. However, it doesn't explicitly state when NOT to use it or name specific alternative tools for different scenarios.

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