cm_create_external_session

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

With only a title annotation, the description carries full burden for behavioral disclosure. It mentions returning a URL but does not disclose whether the session is temporary, requires prior user registration, has rate limits, or involves any destructive side effects. The mutation nature is implied but not clarified.

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 that front-loads the purpose. It is concise with no waste, earning its place efficiently.

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?

Without an output schema, the description should clarify the return value structure, error conditions, or prerequisite state. It does not. For a tool that initiates a session, more behavioral and error context is needed.

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 input schema covers 100% of parameters with descriptions. The description adds no additional meaning beyond what the schema already provides. Baseline 3 is appropriate given full schema coverage.

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 action ('initiate an external single-sign-on login session') and the output ('returning a URL'). The verb 'initiate' and resource 'external single-sign-on login session' are specific and distinct from sibling tools, which mostly deal with CRUD operations on entities.

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 no guidance on when to use this tool versus alternatives, no prerequisites, and no context about scenarios where this SSO login is appropriate. It fails to mention when not to use it or any dependencies.

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