List WWDC Videos

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

readOnlyHint=true already tells the agent this is a safe read. The description adds genuinely new behavioral context — the data is bundled locally with no network access — but says nothing about ordering, pagination behavior for large result sets, or what happens when filters match nothing.

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?

It is a single compact block with no wasted sentences and leads with what the tool returns. It is somewhat crammed with parenthetical asides, which slightly hurts readability, but nothing is filler.

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 four optional params and no output schema, the description does state what each result contains (title, link, transcript/code, topics). It omits any note about result ordering or the effect of the limit default, which is a minor gap for a list tool.

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%, so all four parameters are already documented. The description largely restates those semantics ('year is one year or all', 'hasCode keeps the sessions with, or without, code') without adding syntax or default details beyond the schema, so the 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 states a specific verb (list) and resource (WWDC sessions) and enumerates the returned fields (title, developer.apple.com link, transcript/code flags, topics). It also scopes the data source ('bundled with this server, no network'), which separates it from network-backed siblings like search_wwdc_content.

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?

It routes parameter values to helpers (list_wwdc_years for years, browse_wwdc_topics for topic IDs), which is useful implicit guidance. However, it never says when to choose this tool over alternatives such as search_wwdc_content or find_related_wwdc_videos, so the tool-selection guidance is only implied.

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