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

There are no annotations, so the description carries the behavioral burden. It does convey that the result depends on the active adapter and is 'currently implemented', implying a dynamic, read-only query. However, it does not describe output shape, possible side effects, authentication requirements, or error behavior, leaving some behavioral ambiguity.

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, focused sentence with no filler or repetition. It states the action, the target, and the relevant qualifier ('active') while remaining highly compact.

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?

For a zero-parameter introspection tool, this is nearly complete. The main gap is that the description does not specify the return format or example capability values, and with no output schema the agent must assume the shape. Still, the tool is simple enough that the description gives adequate context for invocation.

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 tool has zero parameters and the schema is fully self-explanatory, so the baseline is 4. The description does not need to add parameter details because there are none to clarify.

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 uses a specific verb ('Get') and resource ('capabilities currently implemented by the active LINE adapter'), clearly distinguishing this from siblings like line_get_status, line_get_messages, and line_send_message. An agent can immediately understand what the tool returns and what scope it applies to.

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?

No guidance is given for when to use this tool versus its siblings. The description does not mention scenarios, prerequisites, or alternatives, so the agent must infer usage from the tool name and description alone.

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

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

With no annotations, the description must carry the behavioral burden. 'Read' clearly signals a non-mutating operation, and the cursor note reveals pagination behavior. Still, it does not disclose rate limits, authentication needs, default ordering, or whether messages are marked as read.

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 short sentences with no filler. The core purpose is front-loaded, and the pagination hint earns its place without verbosity.

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?

The description covers the essential purpose and one parameter's behavior, which is enough for basic invocation. However, with no output schema and no annotations, it leaves the return shape, message ordering, and default limit behavior unspecified.

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 for all parameters. It only explains 'before' as a cursor for older history; 'chat_id' and 'limit' receive no semantic explanation beyond their names and schema constraints.

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 uses a specific verb and resource: 'Read messages from a LINE chat.' This clearly distinguishes the tool from siblings like line_send_message, line_get_status, and line_search_chats, which perform different operations.

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 gives one concrete usage hint: 'Use before as a cursor for older history,' which helps agents paginate. However, it does not explicitly state when to prefer this tool over alternatives or mention any exclusions, so tool-selection guidance is mostly implied.

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

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

With no annotations provided, the description carries the full burden. It clearly indicates a read/query operation ('Get') and describes what is returned ('current state and result'), but it does not disclose polling semantics, error behavior, idempotency, or what occurs when the operation_id is invalid or unknown.

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 one concise, front-loaded sentence with no filler or redundant repetition of the tool name. It efficiently communicates the core action and target resource.

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?

For a single-parameter read operation this is close to adequate, but it omits guidance about how operation_id is acquired and what shape or semantics the returned 'state and result' have. There is no output schema to fill that gap, so the description leaves meaningful ambiguity for an agent.

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 schema describes operation_id only as a string with minLength 1, and the description adds no explanation of what operation_id represents, where it comes from, or how to obtain it. Since schema description coverage is 0%, the description should have compensated, but the parameter is only weakly self-explanatory by name.

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 states a specific verb ('Get') and resource ('asynchronous gateway operation'), and clarifies that it returns 'current state and result'. It is reasonably distinct from siblings like line_get_status by focusing on an operation, though it does not explicitly contrast with them.

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 word 'asynchronous' implies this tool should be used when an agent needs the current state or result of an in-flight gateway operation, which provides some usage context. However, there is no explicit guidance about when to prefer this over sibling tools such as line_get_status, nor any mention of when not to use it.

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

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

There are no annotations, so the description carries the full burden of disclosing behavior. The verb 'Get' reasonably implies a read-only, non-destructive operation, but the description does not explicitly state that it does not modify state, nor does it mention failure behavior or whether it requires a connected Chrome/gateway. This is a minimal but not rich disclosure.

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 no filler. Every word contributes to identifying the exact subject of the status check. It is appropriately sized for a tool with no parameters and no complex configuration.

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?

The tool is simple with no parameters, but there is no output schema and no annotations. The description names the three status areas, which helps, but it does not describe what the returned status looks like or what possible values might be reported. This leaves some ambiguity about how to interpret the result.

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 tool has zero parameters, and the input schema is empty with 100% effective coverage. The description correctly adds nothing about parameters, and no parameter documentation is needed. The baseline of 4 for zero-parameter tools applies.

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 names a specific verb ('Get') and a concrete resource ('the LINE gateway, Chrome CDP, and active LINE page status'), which clearly distinguishes this tool from siblings that handle capabilities, chats, messages, sending, and operations. An agent can tell what this tool does without inspecting schemas.

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 gives no guidance on when to call this tool versus alternatives, nor does it mention prerequisites or conditions like 'use this when checking connectivity' or 'no setup required'. The agent must infer usage entirely from the tool name and description.

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

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

With no annotations provided, the description must carry the behavioral disclosure burden. It only says the tool lists/searches chats and returns IDs; it does not mention pagination, filtering semantics, side effects, authentication requirements, or any limitations. For a no-annotation tool, this is insufficient.

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 short sentences with the core purpose front-loaded and no filler. The downstream usefulness of the returned chat IDs is a valuable addition without any wasted words.

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 zero annotations, no output schema, and 0% parameter coverage, the description is too minimal. It explains what the tool returns conceptually but omits parameter semantics, result shape, and behavioral details, leaving an agent under-informed for correct invocation.

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 schema has 0% description coverage and the description does not mention any of the three parameters (limit, query, unread_only). The agent receives no guidance on how these parameters affect the search or list behavior, so the description adds no parameter-level 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 states a clear action and resource: 'List or search LINE chats.' It also differentiates from sibling tools by clarifying that returned chat IDs are inputs for message tools, which distinguishes it from line_get_messages, line_send_message, and status/capability tools.

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 phrase 'Chat IDs returned here are used by message tools' provides clear context for when to use this tool: before message-related operations. However, it does not explicitly name alternative tools or state when not to use it, so it falls just short of a 5.

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

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

With no annotations, the description must carry behavioral disclosure. It does a good job by explicitly stating the asynchronous nature ('Queue') and the return type ('an operation that can be polled'). This tells the agent that the action is not immediate and provides a follow-up mechanism. It does not disclose side effects, permissions, or failure modes, but the core behavior is covered.

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 short sentences, each earning their place. The first states the primary action, and the second provides the crucial return/polling behavior. No redundant wording and the most important information is front-loaded.

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?

The description covers the essential send-and-poll workflow but is incomplete overall. It does not explain optional parameters, potential side effects, or what should be provided for 'reply_to' and 'idempotency_key.' Given there is no output schema and no annotations, more guidance would be needed for fully confident invocation.

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 does not explicitly explain any parameters. It implies 'text' and 'chat_id' by the phrase 'text message to a LINE chat,' but 'reply_to' and 'idempotency_key' are left entirely unexplained. The parameter names are somewhat self-explanatory, but the description adds little semantic value.

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 states a clear verb and resource: 'Queue a text message to a LINE chat.' This precisely identifies the tool's action and target, and because all siblings are retrieval/status tools, it is unambiguously distinguished as the send operation.

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 implies when to use this tool: when a text message needs to be sent to a LINE chat. However, it does not explicitly state when not to use it or mention any alternatives, though the sibling tools are all read-related and clearly not send alternatives. This is sufficient but not robust.

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