create_eligibility_rule

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

No annotations are provided, so the description must cover behavioral traits. It only discloses that the tool requires 'confirmed: true' to execute, but does not mention idempotency, error states, or side effects like whether the rule is immediately active.

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 consists of two short sentences, each adding value: the first states the purpose and domain, the second provides a critical usage constraint. No filler or 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?

Given 5 parameters, no output schema, and no annotations, the description is too brief. It explains a single behavioral constraint but omits expected return values, error scenarios, or prerequisites beyond 'confirmed: true'. This leaves the agent with significant unknowns.

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 40% with documented parameters 'name' and 'pql_expression'. The description adds the requirement that 'confirmed' must be true, which supplements the schema where 'confirmed' has no description. This somewhat compensates for the low coverage, but the 'access_token' and 'description' parameters remain 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 clearly states the verb 'Create' and resource 'PQL eligibility rule for Experience Decisioning,' which matches the tool name and distinguishes it from siblings like 'create_collection' or 'create_selection_strategy.'

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 mentions a precondition ('Requires confirmed: true to execute') but does not provide explicit guidance on when to use this tool versus alternatives, such as 'create_selection_strategy' or 'create_ranking_formula.'

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