api_endpoint

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

No annotations are provided, so the description carries full burden for behavioral disclosure. The description reveals nothing about what the tool actually does behaviorally - whether it creates, validates, or modifies endpoints; what permissions are needed; whether it's read-only or mutating; what happens on success/failure; or any rate limits. It's essentially a placeholder instruction rather than a tool description.

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, which is appropriately concise. However, it's not front-loaded with critical information - it reads more like an instruction to a human than a tool description for an AI agent. While brief, it wastes its limited space on vague phrasing rather than clear tool definition.

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 with no annotations, no output schema, and a vague purpose, this description is completely inadequate. It doesn't explain what the tool does, what behavior to expect, what the parameter means, or what results are returned. The description fails to provide the minimal context needed for an AI agent to understand and use this tool effectively.

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 description coverage is 100% with one parameter documented as '参数' (parameter). The description adds no parameter-specific information beyond the schema. It doesn't explain what the 'param' parameter represents, what format it expects, or how it relates to 'endpoint information.' With high schema coverage, the baseline is 3, but the description adds zero value regarding parameters.

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 '请根据 RapidAPI 页面手动添加端点信息' translates to 'Please manually add endpoint information based on the RapidAPI page.' This is vague - it doesn't specify what action is being performed (create? update? validate?), what resource is being manipulated, or what 'endpoint information' means. While it mentions RapidAPI context, the purpose remains unclear and lacks a specific verb+resource combination.

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 minimal guidance - it suggests this tool is used when working with RapidAPI endpoints, but gives no indication of when to use it versus alternatives, what triggers its use, or any prerequisites. With no sibling tools, differentiation isn't needed, but the description still lacks basic usage context beyond the RapidAPI reference.

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