Retrieve basic details about the LINE Official Account this bot runs on, including display name, basic ID, and chat mode, so you can verify configuration before running bot operations.
Basic info about the LINE Official Account this bot runs on: display name, basic ID, chat mode.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description usefully discloses the returned fields, but says nothing about auth requirements, rate limits, or whether the bot must be an admin of the account.
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?
A single efficient sentence, front-loaded with the subject (the LINE Official Account) followed by the concrete return fields. No filler.
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-param, read-only lookup with no output schema, listing the returned fields is exactly the right level of detail. Only a brief note on auth/scope would make it fully complete.
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?
Zero parameters, which is the baseline-4 case. Nothing in the description conflicts with or needs to compensate for the empty schema.
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?
States a specific resource (the LINE Official Account the bot runs on) and enumerates what is returned: display name, basic ID, chat mode. It is clearly distinguishable from sibling line_get_profile (user profile) in substance, though it does not explicitly name the alternative.
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 when-to-use or when-not-to-use guidance, and no routing to alternatives such as line_get_profile or line_message_quota. The only hint is the implicit framing that this is an account-identity lookup, which an agent must infer.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.