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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only mentions cost ('This tool is free') but does not state whether the tool is read-only, whether it has side effects, or whether it requires authentication. For a schema retrieval tool, these traits should be made explicit.

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 extremely concise: two short sentences. The first sentence clearly states the purpose, and the second adds the value that the tool is free. There is no wasted wording or redundant information, and it is front-loaded with the action and resource.

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 zero-parameter tool, the description minimally conveys what the tool does. However, it lacks contextual integration with sibling tools, such as explaining that this schema is a prerequisite for purchase or validation calls. It also does not describe the contents of the schema summary beyond the name, and since there is no output schema, additional context about the return format would help. The description is adequate but not rich.

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?

The tool has zero parameters, as shown by the empty input schema. With no parameters to explain, the description does not need to add parameter semantics, and the baseline for 0 params is 4. The description's mention of 'input and output schema summary' gives a hint about what the tool returns, which is sufficient.

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 states a clear action (Get) and a specific resource (the KillionApps platform-neutral promotion allocation input and output schema summary). This immediately distinguishes it from siblings like get_promotion_allocation_offer, which retrieves an offer, and purchase/validate tools that perform actions.

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?

The description provides no guidance on when to use this tool versus its alternatives. It does not mention that the schema might be needed before calling purchase_promotion_allocation or validate_promotion_allocation_request, nor does it give any context for choosing this tool. The only additional statement is 'This tool is free,' which is not usage guidance.

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