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

No annotations are provided, so the description carries the full burden. It does add behavioral context: 'losses kept, corrections dated' signals data honesty and that the record includes negative outcomes and dated corrections. However, it does not state whether the operation is a read-only fetch (implied but unstated), return format, caching, or rate limits. For a no-annotation tool, this is moderate disclosure.

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 content is packed into one dense sentence plus a short imperative. The metrics list is front-loaded and the usage directive is separated cleanly. It is efficient, though the parentheticals slightly burden readability.

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 zero-parameter, no-output-schema, no-annotation tool, the description covers the key behavioral traits (losses kept, corrections dated), the metric set, and a usage precondition. It does not explain the return structure, but since no output schema exists, some guidance on shape would have helped. Overall it is sufficiently complete for an agent to use it correctly.

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?

Parameter count is 0, so the baseline is 4 per the rubric. The description correctly implies no filtering inputs are needed, which is consistent with an empty schema.

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 names the exact resource (Tapeline's public track record) and lists the specific metrics returned: pick count, session count, share beating SPY, median alpha. This is concrete rather than tautological. It does not explicitly distinguish itself from siblings like get_daily_picks or get_ticker_record, though the scope (aggregate public record) is implicitly distinct.

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 final sentence gives an explicit mandatory usage rule: 'Call this before stating any Tapeline performance figure.' This is a clear, actionable precondition that removes ambiguity about when to invoke the tool.

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