get_commission_info

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states that the tool retrieves commission structure and examples, but does not mention whether it requires authentication, if it has side effects (though 'Get' suggests read-only), or what the exact return format is. This is minimal behavioral information.

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 a single sentence with only eight words, all essential. It is front-loaded with the action and resource, and there is no fluff or repetition.

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 has no parameters, no output schema, and no annotations, the description's brevity might be acceptable for a simple read operation. However, it could be more explicit about what 'commission structure' includes (e.g., rates, tiers) and what 'examples' refers to. The name and description together are understandable, but for a full tool in a rich ecosystem, a bit more context would help. It 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 input schema has zero parameters, so the description does not need to explain parameter semantics. The baseline for zero parameters is 4, and the description adds no unnecessary clutter, though it also doesn't need to. Thus a 4 is appropriate.

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 uses a specific verb 'Get' and identifies the resource as 'affiliate commission structure and examples,' clearly stating what the tool does. It is distinct from sibling tools like get_affiliate_info or get_my_affiliates, though it does not explicitly name alternatives.

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 other affiliate-related tools such as get_affiliate_info or get_my_affiliates. There are no context cues or exclusions, leaving the agent to infer based on the name alone.

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