substack_live_blog_start

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

With no annotations provided, the description carries full burden but only states the action without disclosing behavioral traits. It doesn't mention if this requires authentication, has side effects (e.g., creating a public session), rate limits, or what happens after starting (e.g., how to add content). This leaves critical gaps for a tool that likely initiates a mutable state.

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, front-loaded sentence with zero waste—it directly states the tool's purpose without unnecessary words. This is appropriately sized for a simple action, earning full marks for efficiency.

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 of starting a live blogging session (likely a stateful operation with siblings like substack_live_blog_end), no annotations, and no output schema, the description is incomplete. It doesn't explain the tool's role in the workflow, expected outcomes, or how it interacts with other tools, leaving significant contextual gaps.

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 description adds no parameter semantics beyond what the input schema provides. With 100% schema description coverage, the schema already documents both parameters (title and subtitle) clearly. The baseline score of 3 reflects adequate coverage by the schema, but the description contributes no additional meaning.

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 'Start a live blogging session' clearly states the action (start) and resource (live blogging session), but it's vague about what 'live blogging session' entails compared to other drafting/publishing tools. It doesn't differentiate from siblings like substack_create_draft or substack_post_note, which also involve content creation.

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. It doesn't mention prerequisites (e.g., needing a draft or post first), exclusions, or how it relates to siblings like substack_live_blog_end or substack_publish, leaving the agent to infer usage from context alone.

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