Poll Messages

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

No annotations are present, so the description carries the full behavioral burden. It communicates that the tool reads cached messages, but it does not disclose return format, blocking behavior, timeout semantics, side effects, or how 'cached messages' are selected or delivered. This is minimal behavioral disclosure.

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, front-loaded sentence with no filler, repetition, or irrelevant detail. 'Poll', 'cached messages', and 'ntfy topic' all add meaningful information without waste.

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 schema is rich and fully covers parameters, but there is no output schema and no annotations, and the description omits context about the returned messages or behavioral traits of polling. It is adequate for basic invocation, but not fully complete for a 9-parameter tool with no additional structured context.

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 description coverage is 100%, so all nine parameters are already documented in the schema, including filters, the server default, and the effectively required topic. The description adds no parameter-level meaning, so the baseline score of 3 is appropriate.

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 states a specific action and resource: 'Poll for cached messages from an ntfy topic.' It clearly identifies the tool as a retrieval operation and is distinct in intent from the publish sibling. However, it does not explicitly differentiate itself from server_health or name an alternative, so it falls just short of full sibling differentiation.

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 is provided on when to use this tool versus publish or server_health, nor are any exclusions or prerequisites given. The verb 'poll' implies retrieval, but the agent is left to infer the appropriate use case without direct support.

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