get_domains_expired

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

No annotations are provided, so the description must fully disclose behavior. It only states the action without mentioning output format, pagination, rate limits, authentication needs, or whether it's a read-only or mutating operation. For a tool with 63 parameters, this lack of behavioral context is severely inadequate.

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, efficient sentence in French, which is appropriately concise. However, it's under-specified rather than truly concise, as it lacks necessary details. Still, it avoids redundancy and is front-loaded with the core action.

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 high complexity (63 parameters, no output schema, no annotations), the description is completely inadequate. It doesn't cover parameter meanings, behavioral traits, or usage context, making it insufficient for effective tool invocation. The agent would struggle to use this tool correctly.

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 only 3%, with most parameters undocumented in the schema. The description adds no information about parameters, failing to explain the purpose of numerous filters (e.g., 'fb_comments_min', 'total_traffic_max') or how they relate to expired domains. This leaves the agent unable to understand parameter usage.

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 'Obtenir les domaines expirés' (Get expired domains) states the basic action but is vague about scope and functionality. It doesn't specify whether this retrieves a list, filters, or analyzes expired domains, nor does it distinguish this tool from sibling tools like 'get_domains_expired_reveal' or other domain-related tools. The purpose is clear at a surface level but lacks specificity.

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 alternatives. With many sibling tools (e.g., 'get_domains_expired_reveal', 'get_domains_bulk'), the description fails to indicate context, prerequisites, or exclusions. This leaves the agent without direction on tool selection.

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