reminders.list_sources

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

Without annotations, the description must disclose behavioral traits. It states 'list' which implies a read-only operation, but does not specify if the listing is complete or paginated, or any authentication requirements. For a straightforward list tool, this is minimally adequate but leaves some unknowns.

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 extremely concise at only three words. It conveys the basic purpose, but could include a bit more context without losing conciseness. It is front-loaded and to the point.

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 is too brief to be contextually complete. It does not explain what a 'source' or 'account' is in the context of reminders, leaving ambiguity. With an output schema present, it can omit return values, but basic conceptual context is missing.

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% as the only parameter 'include_empty' is fully described in the input schema. The description does not add any additional context about the parameter's meaning or usage beyond what is already in the 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 the action 'list' and resource 'reminder sources/accounts', which distinguishes it from other listing tools like reminders.list_lists and reminders.list_reminders. However, the term 'accounts' might be ambiguous without further context.

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 provides no guidance on when to use this tool compared to other listing tools like reminders.list_lists. It does not explain the purpose of sources or provide context for when a user would need to list them.

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