line_get_capabilities

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.