get_schedule

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

No annotations provided; description discloses output format (JSON array sorted by time) but lacks details on authorization, rate limits, or side effects. Basic transparency for a read operation.

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?

Concise, front-loaded with purpose, then parameter and return details. Every sentence adds value 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?

Given single parameter and output schema existence, the description adequately covers inputs and returns. Could mention that sessions are object details, which likely reside in output schema.

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 has 0% description coverage; description adds critical meaning by listing allowed day values ('monday' (co-located), 'tuesday', etc.) and context, significantly enhancing the bare schema.

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 it gets the full conference schedule for a specific day, listing exact day names and return type (JSON array sorted by start time). It distinguishes from siblings like search_sessions and get_conference_overview.

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?

Provides clear context to use with a specific day parameter, but does not explicitly exclude alternatives or give when-not-to-use guidance. The sibling set implies differentiation.

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