Get broadcast schedule

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

The description adds the optional weekday filter, but annotations already declare readOnlyHint=true and openWorldHint=true, covering safety and open-world assumptions. No additional behavioral details (e.g., pagination, data freshness) are provided, so the description adds minimal value beyond annotations.

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 a single sentence, efficient and front-loaded. Every word earns its place with no redundancy.

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?

The tool is simple with 2 optional parameters and no output schema. The description covers the essential functionality but omits details like pagination behavior or typical output structure, which would be helpful for complete understanding.

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%, meaning both parameters (day, limit) are adequately described in the input schema. The description adds no new parameter-level meaning, so 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 clearly states the tool gets the broadcast schedule, with an optional single-weekday filter. It is distinct from sibling tools like 'get_anime' or 'get_seasonal_anime' which cover different aspects of anime data.

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 description implies usage for fetching schedule data but provides no explicit guidance on when to use this tool versus alternatives. The context is simple enough that a user may infer, but stricter criteria for a higher score would require explicit when-to-use notes.

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