Auth Create Session

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

Annotations already declare readOnlyHint=false, openWorldHint=true, and idempotentHint=false. The description adds one useful contextual warning—'This may create or update Monarch data'—which is consistent with the annotations, but it does not disclose what happens on auth failure, whether tokens are persisted, or any rate/security limits. No contradiction.

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 sentences with no wasted words, but the first sentence merely restates the title and the second is vague ('may create or update'). Compact but low information density.

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 7-parameter auth tool with no output schema, the description omits the auth flow entirely: when mfa_code is required, what include_token means, what trusted_device does, and what a successful session creation returns. The presence of sibling auth_login makes this gap more serious since the agent cannot route between them.

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 only 29% (only fields and output_mode have descriptions). The description adds no parameter information at all, failing to compensate for undocumented params like mfa_code, include_token, and trusted_device—critical for understanding the auth flow.

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, so it is not a pure tautology. However, it does not distinguish this tool from the sibling auth_login or explain what a session is versus a login, and the phrase 'This may create or update Monarch data' clouds the core purpose.

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 given for when to use this tool versus auth_login, auth_save_session, or auth_load_session. There is no mention of prerequisites (e.g., MFA enrollment), when mfa_code or trusted_device are needed, or any exclusions.

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