delimit_toolcard_cache

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

The description discloses side effects: actions like register/clear/flush mutate the cache while others are read-only. It also mentions gating by require_premium. Since no annotations are provided, the description fully carries the burden of behavioral disclosure.

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 concise: three short paragraphs with front-loaded purpose. Bullet points for side effects improve readability. No unnecessary 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?

Given the tool's complexity (3 parameters, multiple actions, output schema exists), the description covers purpose, usage guidelines, side effects, and sibling contrast. Since an output schema is present, lack of return value explanation is acceptable.

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%, so the description is not required to detail parameters. However, it adds context by classifying actions as mutating or read-only, which is valuable beyond the schema. A slight improvement over baseline 3.

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 that the tool manages the tool-schema cache to reduce per-session token waste. The verb 'manage' and resource 'tool-schema cache' are specific. It distinguishes from sibling delimit_help by explicitly contrasting their purposes.

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 provide clear guidance. It explains that the tool is for sending diffs across sessions and not as a runtime dispatcher. The contrast with delimit_help further clarifies usage.

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