gangtise_edb_search

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

No annotations are provided, so the description must carry the behavioral transparency burden. It indicates a read-only search operation, but lacks details on authentication, rate limits, or result behavior (e.g., exact vs fuzzy matching). Given the simplicity of the search, the description is adequate but not exhaustive.

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 with two main parts: a date context note in brackets (important for temporal references) and the core purpose. Every sentence adds value without 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 simple search tool with 2 parameters and no output schema, the description covers the essential purpose and output. It could mention the result format (e.g., list of objects) but is otherwise complete for an agent to use 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 coverage is 100%, and the description does not add new meaning beyond the schema's parameter descriptions. It mentions searching by keyword but no extra semantics for parameters like `limit` (default 100, max 200). The baseline of 3 is appropriate as the schema already explains the 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 clearly states the action (search by keyword), target (行业经济数据库指标列表), and output (指标ID和名称) for subsequent time series data queries. It distinguishes itself from the sibling tool `gangtise_edb_data` which would use the returned IDs.

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 hints at the tool's purpose as a precursor to time series data retrieval ('用于后续查询时序数据'), providing context for when to use it. However, it does not explicitly state when not to use it or mention alternatives among the many sibling tools, leaving some ambiguity.

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