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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so safety is covered. The description adds that the kit is free and includes compliance assets (required disclosure line, do-not-say list), but it omits whether the tool returns text or JSON and how it behaves when code is omitted.

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?

One dense sentence with the key contents front-loaded; 'Free.' is short and informative. The list structure is efficient, though the fragment lacks a verb.

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 one-optional-parameter read tool with no output schema, the description lists the returned sections but does not specify output format or default behavior without a code. Given the tool's low complexity, this is adequate but not complete.

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% for the single optional 'code' parameter (mt-xxxxxx). The description repeats 'for a given code' and ties ref links/MCP config to it, adding slight context about personalization, but does not explain what happens if the code is absent.

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 enumerates specific deliverables—honest descriptions in EN/zh-TW, sample prompts, required disclosure line, do-not-say list, and ref links/MCP config—so an agent can tell it returns a compliance-oriented pitch kit. It lacks an explicit verb (e.g., 'Get' or 'Returns') and does not distinguish it from sibling tools like partner_program, keeping it below a 5.

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 when-to-use guidance or exclusions are given; it does not say to use this before partner_signup or instead of partner_program, nor does it explain the role of the optional code. The agent must infer usage from the sibling names and the content list.

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