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

Annotations cover the safety profile (readOnlyHint=true, openWorldHint=false, destructiveHint=false). The description adds substantial domain context about the store tree structure, slot mechanics, pricing semantics, and the critical constraint that a product not in a slot cannot be bought. However, it doesn't mention any auth requirements or return format. With annotations covering safety, the added domain context is valuable.

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 extremely long and dense, packing domain modeling details (slot modes, pricing options, badge semantics) into a single paragraph. For a simple one-parameter read tool, the vast majority of this content is encyclopedic context that doesn't help the agent invoke the tool correctly. It is not front-loaded in terms of actionable guidance.

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 full schema coverage and no output schema, the description is far more detailed than necessary. It provides extensive domain modeling context but omits practical details like authentication requirements or whether the title_id must correspond to a managed title. It is complete in subject matter but misallocated.

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 only one parameter (title_id), so the schema fully documents the parameter. The description adds no parameter-specific guidance beyond what the schema provides. Baseline 3 is appropriate when schema does the heavy lifting.

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 opens with a specific verb and resource: 'GET ONLY the Store field of TitlePublicConfigurationModel', which precisely identifies the resource and the read-only scope. It differentiates from siblings explicitly by contrasting with get_premium and get_deal_offer. The only slight deduction is that the first clause is somewhat technical (referencing a specific model field).

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 clearly distinguishes this tool from get_premium ('real-money tiered offers') and get_deal_offer ('limited-time promotions with progression'), giving the agent explicit alternatives. It doesn't state when-not-to-use beyond those comparisons, but the context is clear for the store domain.

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