check_subscription_once

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 mentions 'one-time' (implying no persistence) but does not explain side effects (e.g., network request, potential subscription state changes), timeout behavior, or what constitutes success/failure. The description is too sparse for a network-involved tool.

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 with no filler. It is concise and front-loaded with the action ('Fetch a subscription URL') followed by the purpose ('run a one-time connectivity check'). Every word contributes meaning.

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?

Despite the presence of an output schema, the description lacks sufficient context for a 3-parameter tool with no annotations. It does not explain what a subscription is, what a connectivity check entails, or the role of optional parameters. The tool is under-specified for reliable agent selection and invocation.

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 0%, so the description must compensate. It mentions 'subscription URL,' which maps to the `subscription_url` parameter, but it does not explain `timeout_seconds` or `node_name_keyword`. The word 'fetch' adds some context but leaves other parameters undocumented.

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: 'Fetch a subscription URL and run a one-time connectivity check.' The verb 'run' and resource 'subscription URL' are specific. The phrase 'one-time' distinguishes it from sibling tools like `register_subscription_monitor` and `run_monitor_now`, which involve persistent or recurring checks.

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 a one-time ad-hoc check but does not explicitly state when to use this tool versus registering a monitor or triggering an existing one. There is no mention of alternatives or exclusions, so usage guidance is only implicit.

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