Get casts

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

Annotations already provide readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, so the safety profile is clear. The description adds a useful behavioral claim that playerID is applied as WCL sourceID, but 'bounded' is left unexplained and no return or pagination behavior is disclosed.

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 description is only two sentences and stays focused, but it is extremely terse for an 11-parameter tool. The first sentence is vague, while the second sentence is useful but narrow. It is concise, but it sacrifices necessary specification.

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?

This is a complex tool with 11 parameters, no output schema, and many sibling tools, yet the description provides almost no context about result content, scope, or bounding behavior. An agent would need to inspect schemas or sibling tools to understand what 'bounded cast evidence' actually returns.

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 schema already states that playerID 'maps it to the correct source/target filter,' so the description's playerID sentence adds little new meaning. With 64% schema coverage, parameters like abilityID, translate, maxEntries, and maxPayloadBytes lack descriptions that the tool description does not compensate for.

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 says 'Get bounded cast evidence,' which essentially restates the tool name with vague modifiers. It does not explain what a cast is, what report/fight/player scope is covered, or how this differs from siblings like get_character_casts or get_events. The playerID sentence adds parameter detail, not purpose clarity.

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?

There is no guidance about when to use this tool versus alternatives. It does not mention get_character_casts, get_fight_events, or other sibling tools, and no selection conditions are provided. The agent is left to infer when 'bounded cast evidence' is the right choice.

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