signupgenius_list_created_expired

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

Annotations already declare readOnlyHint=true, so safety is covered. Beyond that, the description discloses a genuinely non-obvious behavioral trait: that in v3 the endpoint returns active and expired records together, so the result set is broader than the name implies. It stops short of covering pagination or result size, but the surprise disclosure is real added value.

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?

Two short clauses, front-loaded with the alias relationship and followed by the client-side filtering instruction. Nothing is wasted, though the parenthetical reference to 'session mode' and 'v3' assumes context the agent may not have.

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 zero-parameter read-only list tool with no output schema, the description covers the essential caveat and the client-side filter. It leaves open what happens outside 'session mode' (the description implies the behavior is conditional), and says nothing about pagination or result volume, which matters for a list tool that can return both active and expired records.

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 tool takes zero parameters with 100% schema coverage, so there is nothing for the description to explain and the baseline of 4 applies. The description correctly adds no redundant parameter talk.

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 names the resource (created signups) and explicitly frames this as an alias of signupgenius_list_created_active, which lets an agent place it against the sibling tools list_created_active and list_created_all. However, calling it an 'expired' tool while stating it actually returns active + expired together creates mild ambiguity about what the tool itself does versus what the caller must do.

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?

It gives one concrete usage instruction ('Filter on enddate client-side'), which tells the agent how to obtain expired entries from this call. It does not state when to prefer this over signupgenius_list_created_all or signupgenius_list_created_active, leaving the choice among the three near-identical siblings largely to inference.

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