session_announce

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

No annotations are provided, so the description carries full burden. It comprehensively discloses side effects: registers presence, triggers heartbeat, sweeps sessions after 10 minutes, releases locks, and returns peer sessions for territory coordination.

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?

Informative yet concise, with no superfluous words. First sentence captures the core purpose, followed by critical usage and behavior details in a natural flow.

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?

Despite no output schema, the description covers return value (list of live peer sessions) and all essential behavioral aspects. All three parameters are explained in context, making the tool self-contained.

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% with descriptions for all parameters. The description adds value by explaining territory as an informal claim, session_id defaults, and project_path defaults, enhancing the schema definitions.

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 announces a session on the session bus, registers presence with optional territory, and doubles as a heartbeat. It differentiates from siblings like session_peers by explaining that this tool both announces and returns live peer sessions.

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?

Explicitly advises calling at session start and periodically during long work, and mentions the 10-minute heartbeat timeout. While it doesn't explicitly list when not to use, the context is clear enough for an agent.

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