delimit_toolcard_cache

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

No annotations exist, so description carries full burden. It lists side effects for each action (mutating vs read-only), but does not cover error conditions or authorization needs. Still strong for a cache management tool.

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?

Concise, front-loaded with purpose, followed by well-organized sections for usage, sibling contrast, and side effects. No superfluous sentences.

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?

Covers usage, side effects, and alternative. Output schema exists to handle return values. Lacks prerequisites (e.g., need to register before other actions?) but default action is safe. Good overall.

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%, baseline 3. Description groups actions by side effect (mutating vs read-only), adding some context beyond schema, but does not add meaning for tool_schemas or tool_names beyond what schema provides.

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 it manages a tool-schema cache to reduce token waste, specifies the resource and action, and distinguishes from sibling delimit_help by saying 'this caches tool schemas; delimit_help describes individual tools at runtime.'

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?

Explicit 'When to use' and 'When NOT to use' sections, with a clear alternative (delimit_help) and context (cache side-channel, not runtime dispatcher).

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