get_mikrotik_bgp_connections

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

With no annotations, the description carries full burden for behavioral disclosure. It only states that it retrieves configuration, but does not mention any potential side effects, permissions needed, or constraints. For a read operation, minimal transparency is provided.

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 extremely concise (single sentence), but it sacrifices essential information. Conciseness is only beneficial when the description is still complete enough to guide use.

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 a single parameter with no schema description, no output schema, and no annotations, the tool description should provide more context about the identifier, return format, and differentiation from similar tools. It fails to do so.

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 one required parameter 'identifier' with zero description coverage. The tool description does not explain what the identifier represents (e.g., connection name, IP), leaving the agent with no clue about its 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 uses a specific verb 'Retrieves' and identifies the resource as 'BGP connection configuration', making the purpose clear. However, it fails to distinguish from the sibling tool 'get_mikrotik_bgp_sessions', which likely serves a similar but different purpose.

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 provided on when to use this tool versus alternatives like 'get_mikrotik_bgp_sessions'. The description does not mention context or exclusions, leaving the agent to infer usage without help.

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