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.

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the action without mentioning any side effects, authentication requirements, rate limits, idempotency, or failure behavior. For a tool that sends a notification, this is minimal but not misleading; still, critical behavioral context is absent.

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, concise sentence that states the core purpose without any filler. It is front-loaded with the key action and resource, making it easy to scan. Every word earns its place.

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 tool has 13 parameters, but the schema documents all of them thoroughly. The description provides the basic operation context, and the schema covers parameter semantics. However, there is no mention of typical usage patterns, error handling, or the requirement that 'topic' is effectively required (noted in the schema but not in the description). For a simple send operation, this is adequate but not fully complete given the tool's complexity.

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 input schema provides 100% parameter descriptions, so the description does not need to add parameter details. The description adds no extra meaning beyond the schema, which is acceptable given the comprehensive schema coverage. The baseline 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 clearly states the tool's action: 'Send a push notification to an ntfy topic.' It uses a specific verb (send), a resource (push notification), and a target (ntfy topic), which distinguishes it from sibling tools 'poll' and 'server_health' without needing 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 implies usage context (when a notification needs to be sent) but does not explicitly state when to use this tool versus alternatives. There are no exclusionary notes or references to sibling tools. The purpose is self-evident, but explicit guidance is missing.

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

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states the action and does not mention side effects, network behavior, error handling, or authentication requirements. For a read-only health check, this may be acceptable, but the description provides no additional context beyond the core function.

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 concise sentence that immediately states the tool's purpose. It is front-loaded with the key action and resource, with no unnecessary words or filler.

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 the tool's simplicity (one optional parameter, no output schema, no nested objects), the description is reasonably complete. However, it leaves the exact meaning of 'message statistics' unspecified, and does not clarify whether the health check returns a boolean, a structured report, or something else. This is a minor gap for a health-check 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 schema already documents the single optional 'server' parameter with 100% coverage, so the description does not need to repeat it. However, the description adds no additional meaning or context about the parameter, such as its impact on the health check or examples of valid values, keeping it at the baseline score.

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 checks server health status and message statistics, using a specific verb and resource. It is easily distinguished from sibling tools publish and poll, which have different purposes, though it doesn't explicitly name them.

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 the alternatives. It is implied that this is for health checks, but there are no explicit conditions, exclusions, or references to other tools, leaving the agent to infer appropriate usage.

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