Bootstrap RPS Session

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions that the cookie is never echoed back and returns an opaque session_id, but doesn't cover error handling, idempotency, 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 efficient sentences that front-load the purpose and cover key behavioral details. No unnecessary words.

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?

No output schema, but the description mentions the return value (opaque session_id). For a simple session bootstrap tool, this is sufficient. However, it could note error conditions or prerequisites.

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 50% (only 'cookies' has a description). The description adds minimal value: it mentions the cookie header but doesn't clarify the 'label' parameter's purpose. The parameter semantics rely heavily on the schema.

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 it 'Creates a server-side session from an existing rps cookie header' and specifies the cookie domain 'rps.unibo.it'. This distinguishes it from sibling tools targeting other systems (e.g., Almaesami, SOL, Virtuale).

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 usage when you have an RPS cookie header. It doesn't explicitly state when not to use it or name alternatives, but the context of sibling tools (e.g., almaesami_bootstrap_session) provides differentiation.

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