get_checklist_score

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

No annotations are provided, so the description carries the full burden, and it does disclose what the tool compares and computes. However, it says nothing about permissions, whether the analysis is read-only, time-range defaults, or what the returned structure looks like – gaps that matter for a 3-param analysis tool with zero annotation coverage.

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 purpose statement is front-loaded and the example questions are compact and directly useful for intent matching. Four examples is slightly redundant but each anchors a distinct phrasing, so little is wasted.

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?

There is no output schema, so the description shoulders the burden of explaining return content, and it does so adequately by stating the comparison (win rate and PnL by checklist state). It is reasonably complete for a read-only analytics tool, missing only detail on output shape and defaults.

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 100%, with account, date_from, and date_to each documented in the schema, so the schema does the heavy lifting. The description adds no additional parameter meaning (e.g., defaults for the optional date range or multi-account handling), so the baseline 3 applies.

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 opens with a specific verb and resource: 'Evaluate pre-trade checklist discipline versus trade outcome,' and clarifies the comparison basis (win rate and PnL, checklist completed vs skipped). This clearly distinguishes it from sibling analytics tools like get_emotion_pnl or get_mistake_audit, though it never names a sibling explicitly.

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 four example questions map directly onto the situations in which an agent should call this tool (checklist effectiveness, skip-performance, discipline score, adherence rate). This gives clear context for invocation but offers no exclusionary guidance or named alternatives for related analyses.

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