list_schedule

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

The description mentions it returns {ok, sessions} and lists output fields, but does not disclose behavioral traits such as permissions required, side effects, rate limits, or the significance of the ':9090' port. Since no annotations are provided, the description should reveal more about safe usage.

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 relatively concise and front-loaded with the purpose, then the return format and parameters. However, the mention of ':9090' seems like an internal detail that may not be necessary for the AI agent and adds slight noise.

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 that the output schema exists (mentioned as 'has output schema: true'), the description covers the return structure. Parameters are fully explained. Missing details like pagination, error handling, or default sorting are minor for a simple listing 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?

The description thoroughly explains all three parameters: start and end date formats (YYYY-MM-DD, inclusive) and target_id (filter by object, omit for all of user's own). This adds essential meaning beyond the bare schema, which has no property descriptions.

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's purpose: listing calendar sessions for a given time window, and specifies the returned fields (object name/color, time, lesson title, type, preparation status). It distinguishes from siblings like 'schedule_sessions' and 'update_session' by being a read-only listing tool.

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?

No explicit guidance on when to use this tool versus alternatives, nor any prerequisites or exclusions. Usage is implied by the parameter explanations and the fact that it lists sessions, but no when-to-use or when-not-to-use instructions are provided.

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