Auth Create Session

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

The description adds only 'This may create or update Monarch data,' which is already implied by readOnlyHint=false annotations. No additional behavioral traits (e.g., session management, token handling) are disclosed.

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 a single sentence with no fluff, but it is too vague for a tool with 8 parameters and authentication semantics. Conciseness comes at the cost of completeness.

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?

The description fails to cover the authentication flow, return behavior, or the function of critical parameters. For a tool with no output schema and high parameter count, this is severely incomplete.

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?

With only 25% schema description coverage, the description does not explain the purpose of key parameters like email, password, mfa_code, or session_path. The agent must rely on parameter names alone.

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 states 'Create session' with a clear verb and resource. However, it does not differentiate from sibling tools like auth_load_session and auth_save_session, which could confuse the agent on which tool to use.

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 is provided on when to use this tool versus alternatives, nor any prerequisites or authentication flow context. The agent is left to infer usage from the name alone.

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