context_pack

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the agent knows this is a safe, self-contained read. The description adds genuine behavioral context by stating that the payload includes data freshness and Yahoo access status, which tells the agent the response may reveal staleness or auth problems. It stops short of describing size, ordering, or what happens when data is stale, so it is solid but not rich.

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 imperative 'START HERE every session' is front-loaded and the rest is a tight comma-separated inventory with no filler. It is on the long side, but every listed item is a distinct payload section, so each phrase earns its place.

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?

With no output schema, the description effectively serves as the return-value specification, and it does so by itemizing the payload sections an agent should expect. Combined with annotations covering the safety profile and a zero-argument schema, nothing critical is missing, though flagging which sections may be empty or invalidated by stale data would improve it further.

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 tool takes zero parameters, so per the rubric the baseline is 4. There is nothing for the description to disambiguate beyond noting there are no filters or options, which the empty schema already conveys.

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 (a bundled session context pack) and enumerates its contents: league overview, strategy, playbook, journal, notes, proposals, signals, decision policy, freshness, Yahoo access status. This clearly differentiates it from the many single-topic siblings like league_overview or signals, since it is evidently the aggregate of those. The only weakness is that 'context_pack' itself is not a natural verb+resource phrase; the clarity comes entirely from the enumerated contents.

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?

'START HERE every session' gives an explicit, unambiguous trigger condition, which is strong guidance for an orientation tool. It does not name a when-not or point to alternatives, but for a canonical first-call aggregate that is less necessary — an agent can infer that the individual sibling tools are for follow-up detail.

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