Get Weekly Schedule

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

The description provides detailed behavioral information beyond annotations: it explains timezone conversion logic (converts both time and weekday), grouping of unscheduled shows, and the return format (text digest plus structured content). Annotations (readOnlyHint, openWorldHint) are consistent with the read-only fetching behavior described.

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 concise (5 sentences) and well-structured: it starts with a high-level purpose, then details behavior, and ends with return format. Every sentence adds value without 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 description covers the main functionality, return format, and parameter details. However, it could mention prerequisites (e.g., user must have a watching list) or edge cases (e.g., empty schedule). Still, it is fairly complete given the tool's simplicity.

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 100% with one parameter. The description adds significant context beyond the schema: it explains that the timezone overrides an environment variable and that both time and weekday are converted when a timezone is supplied, enhancing the parameter's meaning.

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 returns a personal weekly airing calendar for anime on the user's watching list, grouped by broadcast day. The verb 'get' and resource 'weekly schedule' are explicit, and it is distinct from siblings like get_my_anime_list.

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 explains when to use the tool (to get a schedule view of currently-airing anime from the watching list) and implies usage context with timezone handling. However, it does not explicitly state when not to use it or compare to alternatives like get_my_anime_list for raw list access.

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