Get RPS Env-Backed Session

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

Discloses that the cookie is never returned and that it returns an opaque session_id. With no annotations, this provides good behavioral context, though it could add details on prerequisites or side effects.

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?

Two concise sentences, front-loaded with action, no redundant information. Every phrase contributes meaning.

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 zero-parameter tool with no annotations or output schema, the description covers the essential: what it does, how it works, and what it returns. Could mention that it establishes a session for subsequent RPS calls.

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?

Zero parameters, so baseline is 4. Description adds value by explaining the purpose and what it returns, clarifying the opaque nature of the session_id.

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?

Description clearly specifies the action ('mints or reuses'), resource ('session_id'), and backing ('RPS_COOKIES env var'). It distinguishes from sibling tools like almaesami_get_env_session by specifying the RPS context.

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?

Implies usage through mention of 'RPS_COOKIES env var', but lacks explicit guidance on when to use this over other get_env_session siblings or when not to use it. No alternatives mentioned.

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