pressable_get_available_addons

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'Get a list,' which implies a read operation, but it does not mention whether any special permissions are needed, whether the list is paginated, or what a typical response looks like.

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, making it very concise and front-loaded. It earns its place by stating the core function, but it borders on under-specification, missing opportunities to add useful context.

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 tool, the description adequately states the primary function. However, it does not explain the meaning of 'available' or differentiate this from the sibling 'pressable_get_account_addons'. The lack of an output schema means the description could provide more detail on the returned list.

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 has zero parameters, so the schema is empty and the description is the only source of parameter-related semantics. It identifies the resource as 'available account add-ons,' which provides some meaning, though it could clarify what 'available' encompasses.

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 action ('Get') and the resource ('available account add-ons'). However, it does not distinguish this from the similarly named sibling tool 'pressable_get_account_addons', which likely lists add-ons already assigned to the account.

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?

There is no guidance on when to use this tool versus the alternative 'pressable_get_account_addons' or any other sibling. No context is provided about what 'available' means (e.g., available for purchase vs. available to the account).

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