pbs_node_subscription_check

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

No annotations provided, so description carries full burden. Clearly states it's a low-impact mutation, dry-run by default, only refreshes cache, no key/identity change. Also specifies the exact return for confirm=True.

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?

Three sentences, front-loaded with key verb and resource. Every sentence adds value: mutation nature, default behavior, execution effect, config dependency. No wasted words.

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?

Missing annotations but description compensates well. Covers behavioral details, return for confirm=True, and config dependency. Output schema exists, so return values for dry-run don't need elaboration. Minor omission: no mention of dry-run output shape.

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 coverage is 100% and schema descriptions are already detailed. Description adds overall context but little extra per-parameter info beyond what's in schema. Baseline 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?

Description starts with 'check and refresh a PBS node's subscription status' – specific verb+resource. Differentiates from siblings like pbs_node_subscription_get by stating 'No key/identity change — status-cache refresh only.'

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?

Explains dry-run by default and confirm=True for execution. Mentions prerequisite 'Needs PROXIMO_PBS_* config.' Does not explicitly contrast with siblings, but the difference is implied through the operation description.

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