capture_status

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

No annotations are provided, so the description carries the full burden. It does not disclose whether the tool reads or writes, whether it requires an active daemon, what happens if port is omitted, or any side effects.

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 short sentence, but it is not well-structured; the phrase 'capture status and session selector' is ambiguous and front-loads unclear purpose.

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 presence of an output schema, return values need not be explained, but the description still fails to clarify the tool's purpose, when to use it, or the parameter's semantics. The description is too thin for a tool with a unique role in a set of nine siblings.

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 description coverage is 0%, so the description must compensate. It only says the port selects a daemon but does not explain the expected format (e.g., number vs string), default behavior, or what happens if the parameter is omitted. This is insufficient for a parameter that is entirely undocumented elsewhere.

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 'Capture status and session selector' is confusing and tautological. It is unclear whether the tool retrieves capture status, selects a session, or both; 'session selector' is not a recognizable verb+resource. It does not distinguish itself from siblings like list_capture_sessions or summarize_session.

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 only hint is 'use port to select one of several daemons,' which is a parameter usage note, not guidance on when to use this tool versus alternatives. No condition, prerequisite, or sibling tool is mentioned.

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