Auth Save Session

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

The description adds that the tool 'may create or update' data, which is consistent with annotations (readOnlyHint=false). However, it does not disclose potential side effects, permission requirements, error conditions, or the nature of the update. Minimal value beyond annotations.

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 very short (two sentences) and front-loaded, but it sacrifices clarity for brevity. It is concise but not sufficiently informative, earning a middle score.

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 lack of an output schema, the presence of sibling tools, and four parameters, the description is grossly inadequate. It does not explain the tool's role in authentication, how to use the 'path' or 'session' parameters, or what the return value looks like. The agent cannot effectively invoke this tool based on this description alone.

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 tool description provides no parameter-level information. With 50% schema description coverage, the description should compensate but doesn't explain what 'path' or the 'session' object fields represent. The agent must rely solely on the schema, which lacks descriptions for critical parameters.

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 says 'Save session' which identifies a specific verb and resource, but fails to clarify what a session is in this context or how it differs from sibling tools like auth_create_session and auth_load_session. The mention of 'Monarch data' is confusing and doesn't align with the auth prefix.

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?

No guidance on when to use this tool versus auth_create_session or auth_load_session. The description provides no context for appropriate usage scenarios or prerequisites, leaving the agent without decision support.

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