Get MCP server and LimeSurvey capability info

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

Annotations indicate read-only, idempotent, non-destructive. The description adds behavioral context: the default no-RemoteControl-call behavior, the probe mode details (list_surveys count, get_site_settings versionnumber), and the superadmin degradation. This exceeds annotation information and clarifies 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 well-structured with key purpose front-loaded, followed by specifics and parameter details. It is relatively lengthy but every sentence adds value. Slight redundancy could be trimmed, but overall efficient.

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 tool's complexity (config reporting with optional probing), the description covers all relevant aspects: default behavior, probe behavior, auth prerequisites, use case guidance, and data fields. With an output schema present, return value explanation is not needed. The description is fully self-contained for an AI 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?

Schema coverage is 100% for the single parameter probe_instance, but the description adds rich semantics: it controls an additional connectivity/auth probe, details what calls are made (list_surveys, get_site_settings), and notes the superadmin requirement and degradation. This goes far beyond the schema's brief description.

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 clearly states the tool reports server-side configuration (server_version, instance_host, etc.) without RemoteControl calls by default, distinguishing it from sibling tools that fetch specific survey data or perform actions. The optional probe_instance parameter is explained, providing a specific resource and action.

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 advises calling this before relying on file export/import or theming tools, and explains when to use probe_instance (for connectivity/auth) and the superadmin requirement for get_site_settings. It implicitly differentiates from siblings by being a configuration-reporting tool.

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