baidu_landmark

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

No annotations are present, so the description bears full responsibility. It only mentions pricing and a free tier, but omits behavioral traits such as accuracy, supported landmark categories, rate limits, or that it is a read-only operation.

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 very concise (one line), but it is front-loaded with the category and purpose. However, it lacks structured information like output format or usage notes, making it minimally adequate.

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 simple tool with one parameter and no output schema, the description does not explain the return value or provide examples. The agent lacks context on what information the tool returns (e.g., landmark name, confidence score, location) and any image constraints.

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 is 100% (the single 'image' parameter has a description '地标图片URL'). The tool description adds no additional meaning beyond what the schema provides, so it meets the baseline for high coverage.

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 '地标识别' (landmark recognition) under a Vision category, clearly indicating the tool identifies landmarks from images. The name 'baidu_landmark' and sibling tools (e.g., baidu_animal, baidu_plant) further differentiate its purpose.

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 alternative vision tools like baidu_object_detect or baidu_ocr. There is no description of prerequisites, preferred image types, or exclusion criteria.

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