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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, and the description is consistent with them. It adds genuine value beyond the annotations by enumerating what is NOT created — session, payment, delivery, outreach — pre-empting an agent from assuming a side effect.

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?

Two short sentences, zero waste, with the unavailability verdict placed immediately after the purpose statement so the agent sees the blocking fact first.

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?

For a parameterless, read-only availability probe with no output schema, the description covers purpose and side-effects adequately. The only gap is that it does not say what the call returns (e.g. a boolean availability flag), which matters precisely because no output schema exists.

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 tool takes zero parameters, so the baseline is 4; there is no argument semantics that need explaining and the description correctly implies a call with no inputs.

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?

"Check subscription availability" gives a specific verb and resource, and the second sentence clarifies the outcome (subscriptions unavailable) plus the negative scope. It clearly separates this stub from sibling lead-feed tools like gisdb_get_stacked_leads or gisdb_export_distress_feed, though it never explicitly names those alternatives.

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 effectively signals 'do not use this to actually subscribe' and tells the agent the outcome in advance, which is useful routing information. However, it never states when an agent *should* call it or which sibling to use instead for obtaining leads.

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