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

No annotations are provided, so the description carries the full burden. It only mentions the expiration condition but doesn't disclose return format, side effects, permissions, or what happens when exporting before or after expiration.

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 with no fluff, but it's under-specified and lacks essential context. It earns a middle score because it is not verbose, yet it doesn't convey enough information to be genuinely useful.

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 and no annotations, the description should explain the export behavior, but it leaves many questions unanswered, such as what 'everything' includes, whether the operation is synchronous, and what happens upon expiry.

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 single 'id' parameter has an empty description in the schema, and the tool description adds no additional detail about its format or meaning beyond implying it identifies a resource. With 0% schema coverage, the description fails to compensate.

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 specifies the action 'export' and the target 'resource', but 'everything under a resource' is vague, and 'before it expires' adds context rather than clarifying what qualifies as exportable content. It doesn't clearly distinguish from related tools like get_resource.

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 given on when to use this tool versus alternatives. The sibling list includes get_resource and extend_resource, but the description doesn't mention them or provide any preconditions, exclusions, or typical use cases.

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