Archive Portal (ADMIN)

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

Annotations declare destructiveHint=true and readOnlyHint=false, which signals this is a mutating/destructive operation. The description adds only 'Requires an ADMIN key' beyond annotations, but doesn't explain what archiving actually does (does it hide the portal? is it reversible? does it affect published state?). For a destructive admin tool, this is a thin disclosure given no rich behavioral context 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 two short sentences with zero waste. The ADMIN key requirement is front-loaded and relevant. It's concise, though potentially too spare given the parameter and behavioral gaps.

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?

With no output schema, destructive annotations, undefined dryRun semantics, and no distinction from delete/unpublish tools, the description is insufficient. A destructive admin operation needs to clarify reversibility, effect on the portal's published status, and the dryRun parameter's behavior. The dryRun parameter alone is a significant completeness gap.

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 description coverage is 0%, and the description mentions neither parameter. There's a 'dryRun' boolean parameter whose semantics are completely undocumented — the agent has no way to know if dryRun prevents the actual archive or what it returns. The portalRef is self-explanatory, but dryRun absolutely requires explanation that is entirely absent.

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 states the tool archives a portal, which is a clear verb+resource pairing. However, it doesn't distinguish this from sibling tools like kilango_delete_portal, kilango_unpublish_portal, or kilango_update_portal — the archiving semantics vs. deletion vs. unpublishing are unclear. The title labels it ADMIN but the description doesn't explain what archiving means in contrast to these related operations.

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 notes it 'Requires an ADMIN key,' which is a prerequisite, but provides no when-to-use guidance, no exclusions, and no alternative tool references. For a destructive admin action with several adjacent sibling tools (delete, unpublish), the agent gets no help deciding when to use this vs. alternatives.

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