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

Annotations mark the tool as destructive. The description adds behavioral context: requires 'confirm' set to 'PUBLISH' to prevent accidental publishing, notes FREE businesses cannot use it, and mandates permission checks. This goes beyond what annotations provide.

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 front-loaded with the main purpose and then lists prerequisites. It is reasonably concise, though the second sentence could be integrated into parameter semantics. Overall, it is well-structured and not overly verbose.

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 complexity (35 parameters, nested objects, no output schema), the description misses crucial details such as return values, error handling, and what happens when a session is already published. It covers usage conditions but not the tool's comprehensive behavior.

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 35 parameters and 0% schema description coverage, the description only clarifies the 'confirm' parameter. It mentions 'full LPBE session editor payload' but does not explain any other parameter, leaving the agent to guess the meaning of many required and optional fields.

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 tool publishes a one-on-one session using the LPBE session editor payload. It specifies the action and resource, distinguishing it from siblings like create_session, update_session, and unpublish_session. However, the term 'one-on-one session' could be more explicitly defined.

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 explicit prerequisites: check business permissions, verify FREE business status, call check_business_tool_access, and handle grace-period warnings. It instructs never to proceed when access is blocked. It does not explicitly compare to other publish_* tools, but the context is sufficient for sessions.

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