rvtdocs_session_set

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

Without annotations, the description adds a behavioral trait: 'Data is ephemeral (lost on server restart).' This informs the agent about persistence, which is valuable beyond the input schema.

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?

Extremely concise: two sentences. Front-loaded with core action. 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?

For a simple session store with two required params and no output schema, the description covers purpose and ephemerality. Missing error handling or data type details, but mostly adequate.

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%, and the description adds no meaning beyond parameter names 'key' and 'value.' It fails to specify allowed formats or constraints.

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 'Store a key-value pair in the session store,' specifying the verb and resource. It distinguishes from sibling tool rvtdocs_session_get.

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 context: 'Useful for caching resolved API info between tool calls,' indicating when to use it. It implicitly suggests using rvtdocs_session_get for retrieval, though no explicit exclusion.

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