athena_longitudinal_tmle_crossfit

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

With no annotations, the description must carry the behavioral burden. It discloses the cross-fitting procedure, bounding, and validation approach, but omits return values, error conditions, and side effects. The scope caveat is useful but the operational behavior is not fully transparent.

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 dense sentences that front-load the core method and add a scope caveat, with no wasted words.

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?

The tool is complex with 11 parameters, nested objects, and no output schema, yet the description provides only a two-sentence summary. It fails to explain required inputs, how to interpret results, or the assumptions behind the method.

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% and the description explains none of the 11 parameters such as treatment1, intermediate, treatment2, regimes, assumptions, or propensity_clip. The phrase 'two-timepoint' is too high-level to map to any specific parameter.

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 uses a specific verb ('Cross-fit') and a precise resource ('bounded binary two-timepoint sequential logistic TMLE'), with details on held-out folds and baseline/time-order validation. This clearly distinguishes it from general longitudinal TMLE tools like athena_longitudinal_tmle.

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 gives some context by scoping to bounded binary two-timepoint sequential designs and warning that it is 'Assumption-scoped; not a general longitudinal TMLE theorem.' However, it does not explicitly state when to prefer this over alternatives or list exclusion criteria, leaving the guidance partial.

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