athena_longitudinal_tmle

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

With no annotations, the description must carry the full burden of behavioral disclosure. It provides only a high-level caveat about being assumption-scoped, but fails to disclose what the output looks like, what assumptions are required, whether it is read-only or has side effects, or what failure modes might occur. For a complex statistical tool, this is insufficient transparency.

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 exceptionally concise, consisting of two sentences that each add value: the first states the core action, target, and method; the second qualifies the scope. There is no filler or redundant information, and it is front-loaded with the most important information.

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 complexity (9 parameters, no annotations, no output schema, and many closely related sibling tools), the description is far too brief. It does not specify assumptions, output format, parameter meaning, or differentiating use cases. An agent would struggle to correctly invoke this tool or choose it over similar longitudinal TMLE tools.

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 and the description does not explain any of the 9 parameters directly. It hints at the roles of treatment1, treatment2, and outcome through the purpose statement, but leaves samples, intermediate, assumptions, propensity_clip, regimes, and baseline undefined. It does not compensate for the lack of schema descriptions.

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 tool's function: 'Estimate static two-timepoint binary treatment-regime risks' with a specific method 'sequential logistic targeting'. It distinguishes itself from siblings by specifying 'static' (vs dynamic), 'two-timepoint' (vs general longitudinal), and 'binary treatment', while also noting it is 'not a general longitudinal-TMLE theorem', which separates it from more general tools.

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 implies usage for static two-timepoint binary treatment-regime risk estimation and warns that it is 'assumption-scoped'. However, it does not explicitly state when to use this tool over alternatives like athena_longitudinal_tmle_crossfit or athena_longitudinal_gformula, nor does it provide exclusion criteria or specific use cases beyond the general purpose.

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