athena_command_start

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

No annotations are provided, so the description carries full burden. It discloses that the tool returns a session ID and must be called once per invocation. It does not mention any side effects, destructive behavior, or idempotency. For a marker tool, this is adequate but lacks some detail.

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, no wasted words. Front-loaded with the core action. Each sentence provides essential information about usage, return value, and pairing with another tool.

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 no output schema, the description correctly reports the return type (session ID) and its downstream use. It covers constraints (one call per invocation, applicable commands) and is sufficient for an agent to use the tool correctly.

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 coverage is 100% and the description adds valuable context: for 'command' it clarifies format and special case 'ad_hoc'; for 'argSummary' it explains non-PII and categorical nature. This significantly aids correct parameter usage.

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's purpose: 'Mark the start of a slash command invocation.' It specifies the verb 'mark' and the resource 'start of a slash command invocation', and lists example commands. It distinguishes from the sibling 'athena_report_outcome' by noting the returned session ID is passed to it.

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 explicitly says 'Call this as the first action in every athena slash command' and lists specific commands. It also says 'One call per invocation'. However, it does not explicitly state when NOT to use this tool versus alternatives among siblings, though the unique role is implied.

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