cpp_fixed_effect_meta

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

No annotations exist, so the description carries the full burden. It does usefully warn that heterogeneity and bias are NOT assessed, which prevents over-interpretation of results, but it says nothing about preconditions, error behavior, or what the pooling returns for sparse/one-study input.

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?

A single compact clause with zero padding, and the caveat is front-loaded. Its brevity is achieved by omitting essentials rather than by editing, so it is concise but under-specified.

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 statistical pooling tool with an unconstrained nested input, no output schema, and no annotations, an agent cannot construct a valid call or interpret the result from this description alone. The scope caveat is the only substantive content.

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 0% and the single parameter 'studies' is an untyped array of free-form objects with no item schema. The description does not say what fields each study object must contain (effect size, variance/SE?), which is the one thing an agent most needs here.

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?

States a verb-resource pair ('fixed-effect numerical pooling') and the implementation flavor ('C++'), which hints at what it computes. However, 'Opt-in' is unexplained and the description never explicitly contrasts with the sibling cpp_random_effects, so the agent must infer the fixed-vs-random distinction itself.

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 on when to choose this over cpp_random_effects or any other pooling path. 'Opt-in' is the only conditional signal and it is never defined (opt-in with respect to what setting or caller?).

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