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

Goes well beyond the annotations (readOnly=false, idempotent=false, destructive=false): it discloses exactly what data is persisted (chain, item, note), that no personal information is kept, that requests are counted rather than displayed publicly, and that fulfillment is not guaranteed. These are real behavioral facts an agent could not derive from the structured fields.

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?

Front-loads the action, then the precondition, then expectations; every sentence carries weight. It runs slightly long at five sentences, but no sentence is filler or repetitive.

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?

For a simple three-parameter write with no output schema, the description covers intent, prerequisites, storage/privacy and likely outcome. It stops short of describing error behavior or what a successful submission returns, but nothing essential to correct invocation is missing.

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% and all three properties carry their own descriptions with maxLength and examples, so the baseline is 3. The description only adds that these are the sole stored fields, which is context but not new per-parameter meaning.

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?

States a concrete verb and resource: telling the site operator that a chain or menu item is missing. It is immediately distinguishable from list_chains/search_menu/sum_items, which are read/lookup tools, because this one files a request.

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?

Gives an explicit precondition ('Use only after search_menu / list_chains could not find it AND the user actually wanted it') naming the exact sibling tools to try first, plus the constraint 'One request per chain or item'. An agent knows precisely when this fires and when it must not.

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