get--v3-domain_name-complaints-address

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

With no annotations provided, the description carries full burden for behavioral disclosure but offers none. It doesn't indicate whether this is a read-only operation, what permissions might be required, whether it returns structured data, or any error conditions. 'Lookup' implies a query but provides no behavioral context about what the tool actually does beyond the minimal verb.

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 (two words) and front-loaded, but this conciseness comes at the cost of severe under-specification. While there's no wasted text, the description fails to provide necessary information that would require more content. It's technically efficient but substantively inadequate.

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 a tool with 2 required parameters (0% schema coverage), no annotations, no output schema, and multiple similar sibling tools, the description is completely inadequate. It doesn't explain what the tool returns, how to interpret results, what the parameters represent, or when to choose this tool over alternatives. For a lookup operation with specific parameters, this leaves the agent with insufficient guidance.

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?

The schema has 0% description coverage for both required parameters (domain_name and address), and the description provides absolutely no information about what these parameters mean, their format, or their relationship. The description doesn't even mention that parameters exist, let alone explain their semantics. This leaves both parameters completely undocumented.

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 'Lookup complaint record' restates the tool name (which contains 'complaints') without adding specificity. It doesn't clarify what type of complaint record, what domain it relates to, or what distinguishes it from sibling tools like 'get--v3-domain_name-complaints' (without address parameter). The verb 'lookup' is generic and doesn't provide meaningful differentiation.

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 zero guidance on when to use this tool versus alternatives. There's no mention of prerequisites, appropriate contexts, or comparison to sibling tools like 'get--v3-domain_name-complaints' (which appears similar but lacks the address parameter). The agent receives no usage direction.

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