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

The description goes well beyond the annotations: it states the blotter is hypothetical ('what the rule would have traded at the next close'), that ETFIQ places no orders, and adds an anti-instruction caveat about the content. It also discloses the blotter_limit default (10) and bounds (0 to 50), which annotations cannot convey. This is exactly the kind of behavioral context that lowers the burden on readOnlyHint/idempotentHint.

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 scope statement is front-loaded and every clause carries information, but the opening sentence is a long run-on list of returned fields that takes effort to parse. Nothing is redundant, yet splitting the field enumeration from the paper-only caveat would improve scanability.

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 must carry the return contract, and it does: it enumerates signals, holdings percentages, dates, last moves, and the blotter with its limit. Combined with the paper-only disclaimers, an agent can decide on and call this tool without further information.

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 50%: slug is documented in the schema as 'A slug from strategy_list', while blotter_limit has no schema description at all. The description compensates for that gap by giving the parameter's meaning, its range (0 to 50), and its default (10), which the schema omits. It does not explain slug format beyond the source tool, so a 4 rather than 5.

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 a specific resource (one Strategy Lab strategy) and enumerates the returned content: per-fund signals with distance from the line, target holdings in percent, next signal and trade dates, last moves, and the paper blotter. That is far more than a restatement of the name. It does not distinguish itself from the sibling strategy_record, which plausibly overlaps, so it falls short of a 5.

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?

Useful context is implied: the tool is a read of 'today's state' and requires a slug 'from strategy_list', which tells the agent where the identifier comes from. However, there is no explicit statement of when to use this versus strategy_record or strategy_list, and no exclusion conditions, so usage is only inferred.

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