nexo_reminders

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

No annotations are provided, so the description carries the full burden. It does not disclose whether the tool is read-only, what side effects exist, or what format the response takes. 'Check' implies a read operation, but this is not explicit.

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 sentence, which is concise but not front-loaded with critical information. It states the core action but omits essential details like the filter parameter. It is adequate but not well-structured for quick comprehension.

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 1 parameter, no output schema, no annotations, and many sibling tools (e.g., nexo_reminder_get, nexo_followup_get), the description is incomplete. It does not explain what 'reminders and followups' means in this context, how the filter works, or what a typical response looks like. It leaves significant gaps.

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 does not mention the 'filter' parameter at all. Schema coverage is 100% with the parameter description listing values, but the tool description adds no additional meaning beyond the schema. It fails to clarify how the filter affects results or provide usage examples.

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 'Check reminders and followups' is a verb+resource pair but lacks specificity. It does not distinguish from sibling tools like nexo_reminder_get or nexo_followup_get, which could also be interpreted as 'checking'. 'Check' is ambiguous—does it mean list, view, or verify?

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 guidance on when to use this tool vs alternatives like nexo_reminder_list, nexo_reminder_get, or nexo_followup_get. There is no mention of context or exclusions, leaving the agent to infer usage from the name alone.

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