set_subscription_price

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

With no annotations provided, the description carries full responsibility for disclosing behavior. It only states 'Set a price point,' which implies a mutation but does not mention side effects like replacing existing price points, whether startDate can be immediate, or any required prior setup. This is minimal disclosure for a write operation.

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 one short sentence, fully front-loaded with the action and object. It contains no wasted words. However, it is so brief that it leans toward under-specification, preventing a 5.

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 complexity (3 parameters including a nullable startDate), no annotations, and no output schema, the description is insufficient on its own. It does not explain the concept of price points, when the price takes effect, or how this relates to subscription groups or other subscription operations. An agent would need to infer much from the schema and sibling tool 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%, with each parameter clearly documented (e.g., startDate, pricePointId, subscriptionId). The description adds no additional meaning beyond the schema, so the 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?

The description uses a specific verb ('set') and resource ('subscription') with 'price point' clarifying the target object. It clearly differentiates from sibling tools like set_iap_price (in-app purchases) and update_subscription (general updates). However, it doesn't mention the optional startDate behavior, leaving a small ambiguity in the precise action.

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 when-to-use guidance is provided. The description does not mention alternatives or exclusions, such as when to use set_subscription_price versus update_subscription or set_iap_price. The intended context is only implied by the tool name and description.

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