get_favorite_store

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

With no annotations provided, the description carries the full burden. The verb 'Retrieves' implies read-only, and it adds authentication requirements and lists the returned store fields. It does not explicitly mention side-effect absence or error behavior, but for a simple getter this is adequate.

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 front-loaded with the main action, followed by a concise enumeration of return fields and the auth requirement. The list is slightly long but every item adds useful context; no empty filler.

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 zero-parameter read tool with no output schema, the description provides context (authenticated user, Carrefour France), describes return fields, and states a prerequisite. It is generally complete, though it could mention empty-result behavior or explicitly confirm no side effects.

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?

Tool has zero parameters and the schema is 100% covered. No parameter descriptions are needed, and the baseline of 4 applies. The description adds no unnecessary parameter details.

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 ('Retrieves') with a clear resource ('favorite/preferred store on Carrefour France') and even enumerates the returned details. This clearly distinguishes it from sibling tools like get_eligible_drive_stores or get_store_information_inserts by focusing on the authenticated user's favorite store.

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?

It states a key precondition: 'requires an authenticated Carrefour session'. This gives clear context for when to use the tool. However, it does not explicitly name alternatives or provide when-not-to-use guidance, though the scope is unambiguous among siblings.

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