get_today_schedule

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

With no annotations, the description alone must convey behavioral traits. It only restates the tool's purpose with 'PW lecture' and does not disclose return format, empty-day behavior, timezone assumptions, or any side effects. The 'get' verb implies read-only, but that is not explicitly confirmed.

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, front-loaded sentence with no filler or redundant wording. Every term ('Get', 'today's', 'PW lecture schedule') contributes meaning.

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?

For a zero-parameter read-only getter, the description is nearly complete: it names the resource and the time scope. It would benefit from noting what happens when no schedule exists or clarifying timezone, but these are minor 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?

The tool accepts zero parameters and the input schema is empty, so there are no parameter semantics for the description to explain. The baseline of 4 applies because there is no parameter documentation gap to 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 specifies the verb 'Get' and resource 'today's PW lecture schedule', making it clear the tool returns the current day's schedule. The 'today's' scope distinguishes it from get_upcoming_schedule and get_next_lecture, though it does not explicitly differentiate from get_schedule or detail what a schedule entry contains.

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 word 'today's' implies when to use this tool: when the agent needs the current day's lecture schedule. However, it provides no explicit guidance about alternatives or when not to use it, such as pointing to get_upcoming_schedule for other time ranges.

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