rti_set_session_url

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

With no annotations provided, the description carries full responsibility for disclosing behavior. It explicitly mentions two side effects: 'replacing any previous one and clearing cached data.' This gives the agent critical information about the destructive nature of the operation, though it does not mention rate limits or other potential 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?

The description is compact: two sentences, with the first covering the action and the second providing usage context. Every word contributes, with no redundant or vague phrases.

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?

Given the tool's simplicity (one parameter, output schema present), the description covers the essential context: purpose, replacement/cache behavior, when to use, and where the URL comes from. The output schema handles return values, so nothing critical is missing.

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?

The schema provides only a bare 'url' string with no description (0% coverage). The description compensates by explaining the source of the value: 'copies the full address-bar URL' from the user's browser. This adds meaningful context that the schema lacks.

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 tool's function: 'Store a new RTI Online View History session URL' with specific actions 'replacing any previous one and clearing cached data.' It distinguishes itself from siblings by focusing on setting the session URL, which is unique among the listed tools.

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 provides a clear scenario for use: 'Use when the old URL stops working' followed by the exact user steps. It does not explicitly mention alternatives or exclusions, but the 'when' context is strong enough to guide an AI agent.

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