get_unread_notification_count

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

Input schema includes limit/offset parameters typically associated with list endpoints, but description only mentions count. No clarification on whether the tool returns a count object or a list with count. No output schema provided. Lack of annotations makes this ambiguous.

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?

Single sentence with dash, but includes stray '[query]' which is confusing. Adequate length, but clarity suffers from the unnecessary bracket.

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?

Tool has 6 parameters and no output schema; description does not explain how parameters affect the count (e.g., filter, type). Missing details on whether count is global or per user. Incomplete for effective use.

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 descriptions cover all 6 parameters with basic meanings (limit, offset, filter, type, notification_id, agent_id). Description does not add further semantic value beyond the schema. Baseline 3 due to high schema coverage.

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?

Description clearly states the tool counts unread notifications using specific verbs 'Contar' and 'obtiene el numero'. It distinguishes from siblings like list_notifications and mark_notification_read.

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 versus alternatives. Does not mention that it returns a count only, nor specify prerequisites or scenarios.

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