list_organization_discounts

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

There are no annotations, so the description must carry the burden of behavioral disclosure. It indicates a read-only listing operation, but does not mention pagination via continuation, the effect of the code filter, or how scope changes the result set. These are meaningful behavioral details an agent would need.

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 short and front-loaded with the core purpose, followed by a useful scope hint. It contains no filler or redundancy. However, it is so terse that it sacrifices necessary parameter and pagination context.

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?

An output schema exists, so return value structure is covered, but the description is incomplete for a paginated list endpoint. It fails to explain the continuation parameter, the meaning of code, or how the scope values affect results. An agent could not reliably fetch all discounts or apply intended filters.

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 description coverage is 0%, and the description only partially compensates by noting scope values 'event' or 'organization.' It does not explain organization_id, code, or continuation beyond what their titles imply. This leaves the filtering and pagination parameters under-specified.

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 specific verb and resource: 'List promotional discounts and access codes under an organization.' This clearly conveys the operation and scope. It is distinguishable from sibling tools like get_discount and create_organization_discount by the plural listing intent, though it does not explicitly call out any sibling.

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 gives no guidance on when to use this tool versus alternatives such as get_discount, create_organization_discount, update_discount, or delete_discount. Usage is only implied by the tool name and the phrase 'under an organization,' with no exclusions or selection criteria.

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