p0010058_query_business_basic_deep

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It states the tool performs a 'deep' query but does not clarify what 'deep' entails, such as scope of data, rate limits, authentication requirements, or if the operation is safe read-only. Basic query intent is implied but not explicitly stated.

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 front-loaded sentences. It efficiently conveys the core purpose and parameter selection rule without wasted words, though it could benefit from a clearer structural breakdown.

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?

Given the tool has 5 parameters, no schema descriptions, and an output schema exists, the description is insufficient. It does not explain what 'deep' means, what data the query returns, or that only one identifier should be provided. The output schema exists but the description does not reference or complement it.

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 0% with no parameter descriptions. The description adds value by explaining the rule that one of four identifiers must be used ('四选一'), but it does not describe the format or constraints of each identifier, nor does it explain the 'extra_params' field. Partial compensation.

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 queries basic business information (deep) and lists the four acceptable identifier types. However, it does not explicitly differentiate from the sibling tool 'p0010010_query_business_profile', though 'deep' suggests a different scope.

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 indicates that exactly one of four identifiers should be provided ('四选一') but provides no guidance on when to use this tool versus alternatives like fuzzy search or business profile query. No prerequisites or exclusion criteria are mentioned.

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