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

Goes well beyond the annotations (readOnlyHint=false, idempotentHint=true) by explaining that retries with the same request_id never add a second rating, that the result is the Edge closing line, that the server identifies the skill from request_id, that notes over 280 characters are truncated, and that a Pro key gates the task block. This is unusually rich behavioral disclosure for a mutation 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?

Purpose and the 'call once, after the work' instruction are front-loaded, but the rest is a single ~350-word run-on paragraph mixing outcome rules, scoring, privacy, Pro-key fields, and error handling. Almost every sentence carries content, yet the wall-of-text structure hurts scannability.

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?

Very complete for a 7-parameter tool with nested objects: it covers outcome vocabulary, score bands, reason defaults, component ids, the optional task report, privacy constraints, idempotency, and host-blocked fallback. No output schema exists, and the description still notes that Edge returns the user's weekly tally.

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 86%, so the baseline is 3; the description earns a bump by spelling out cross-parameter couplings the schema does not, such as which outcomes permit a score, omitting score for wrong_skill/loaded_not_used/unclear, and requiring the note for scores 0-2 and 9-10. It largely mirrors the schema's per-field text, so it is not a full 5.

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 specific verb and resource ('Records only an Edge rating of a skill you used') and immediately delimits what it is not: it does not change files, task output, or act outside Edge. An agent can distinguish it from siblings like report_issue and use_skill from the text alone.

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 explicit timing ('call it once, after the work rather than right after loading'), conditions for skipping ('If the host blocks the call, finish without it'), and names the alternative tool for Edge problems ('use report_issue instead'). When-to-use, when-not, and the alternative are all present.

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