ExportManagedServers

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states 'Export' which implies a read-only operation likely generating output, but it doesn't specify if this requires permissions, what the output contains (e.g., file format, data scope), or any side effects like rate limits. The description is minimal and lacks critical behavioral details for safe invocation.

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, efficient sentence with no wasted words. It is appropriately sized and front-loaded, directly stating the tool's purpose without unnecessary elaboration, making it highly concise and well-structured.

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 complexity (1 parameter with nested objects, no output schema, no annotations), the description is incomplete. It doesn't explain what 'configurations' entail, how to use the 'body' parameter, or what the export produces. For a tool with undocumented parameters and no structured guidance, this minimal description fails to provide sufficient context for effective use.

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 input schema has 1 parameter ('body') with 0% description coverage and no details in the schema. The description provides no information about parameters, such as what 'body' should contain (e.g., filters, options for the export). With low schema coverage and no compensation in the description, parameter understanding is inadequate.

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 'Export managed server configurations' clearly states the action (export) and resource (managed server configurations), which is better than a tautology. However, it lacks specificity about what 'configurations' include or the output format, and it doesn't distinguish this tool from sibling export tools like ExportCloudCredentials or ExportJobs, making it somewhat vague.

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 provides no guidance on when to use this tool versus alternatives, such as other export tools (e.g., ExportCredentials, ExportJobs) or related tools like GetAllManagedServers. There is no mention of prerequisites, context, or exclusions, leaving usage entirely implied from the tool name alone.

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