uber_eats_switch_profile

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

No annotations are provided, so the description carries the full burden. It implies a state-changing operation (switch profile) but doesn't disclose consequences: does it affect subsequent operations, cart contents, or session state? Does it require prior authentication? The only disclosed behavior is that profile_uuid must reference an existing listed profile, which is useful but minimal.

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 concise — two sentences plus a clean Args block. Every word earns its place, and the docstring-style format is well-structured and front-loaded with the core purpose statement.

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?

An output schema exists, so return-value explanation isn't needed. The tool is simple (1 param, no nested objects), and the description covers what's needed to invoke it correctly. The missing piece is behavioral context (side effects of switching), but for a simple state-switching operation this is reasonably complete.

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 0%, so the description must compensate. It explains that profile_uuid is the UUID from list_profiles — a genuinely useful semantic beyond the schema's bare 'Profile Uuid' title. With only 1 param, the description provides enough to disambiguate, though format validation (e.g., valid UUID format) is not mentioned.

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 verb (switch) and resource (active Uber profile by UUID), distinguishing it from profile-listing (uber_eats_list_profiles) and login tools. It's specific and actionable, though it doesn't contrast against the obvious sibling.list_profiles beyond mentioning it as the source of UUIDs.

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 mentions the UUID comes from uber_eats_list_profiles, which implies the sequence of listing then switching. However, it doesn't give explicit when-to-use or when-not-to-use guidance, nor does it address the context where this might matter (e.g., before placing orders or checking whoami).

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