ls_get_subscription_item

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

Annotations already indicate readOnlyHint=true and idempotentHint=true, so the 'Get' action is consistent. The description adds context about included data (quantity, pricing, subscription) but does not disclose potential error responses or rate limits. Given annotations cover safety, this is good.

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?

Single sentence, no redundancy, front-loaded with key action and resource. Every word earns its place.

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 simple read tool with good annotations and clear params, the description is mostly complete. It lacks details on error handling or return structure beyond the summarized fields, but the output schema is absent. Acceptable given the tool's simplicity.

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% with clear parameter descriptions. The description adds value by summarizing typical returns (quantity, pricing, subscription), which relates to the object structure. However, it does not explicitly clarify the relationship with the 'include' parameter.

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 retrieves a specific subscription item by ID, including quantity, pricing, and associated subscription. This distinguishes it from sibling tools like ls_list_subscription_items (list all) and ls_update_subscription_item (update), providing a concise purpose.

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 use when you have a specific subscription item ID and need detailed info. However, it does not explicitly state when not to use it (e.g., for multiple items, use list). The context is sufficient but lacks exclusionary guidance.

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