partial_export_realm

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 disclosing behavior. 'Export' suggests a read operation, but it doesn't clarify side effects (e.g., does it create a file? Return data? Modify state?). The description is silent on output format, atomicity, or any constraints. Minimal transparency.

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 sentence of six words, which is concise. However, it sacrifices completeness for brevity. It is front-loaded with the core purpose but lacks elaboration. A sentence longer but more informative would be better, but conciseness alone is not penalized heavily.

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 lack of output schema and annotations, the description should compensate by explaining the nature of 'partial export', how the boolean parameters interact, and what the result looks like. The tool has 3 parameters and is part of a large set of sibling tools; the description fails to provide sufficient context for correct usage.

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% with descriptions for all three parameters (realm, exportClients, exportGroupsAndRoles). The description adds no additional meaning beyond the schema, as it merely repeats the concept of 'partial export'. Baseline 3 is appropriate for high schema coverage.

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 'Partial export of the realm configuration' specifies the verb 'export' and resource 'realm configuration', but 'partial' is vague and doesn't clarify what is included. The input schema parameters hint at selective export, but the description does not explicitly state that it exports only selected components (clients, groups/roles). It distinguishes from siblings like 'export_identity_provider_broker_config' but lacks specificity.

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 (e.g., get_realm, export_identity_provider_broker_config). It doesn't mention scenarios where partial export is appropriate or when to prefer other export tools. No context on prerequisites or limitations.

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