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

Discloses that consent is required, which is a key behavioral trait. However, with no annotations provided, it does not cover potential side effects, scope of changes, or whether the operation is reversible.

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?

Two short sentences, front-loaded with the action and allowed values. Every word earns its place without redundancy.

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?

Adequate for a simple mutation tool with two parameters, but lacks details on return value, confirmation, or how to obtain consent. Without annotations or output schema, more context would be beneficial.

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?

Adds meaning by enumerating the valid listing_status values and mentioning consent, but does not explain program_id beyond its schema definition. With 0% schema description coverage, it partially compensates but remains incomplete.

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?

Clearly specifies the action (set the listing status) and the resource (a program). Lists the exact allowed values, distinguishing it from sibling tools like org_update_program or org_archive_program.

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?

Provides no explicit guidance on when to use this tool versus alternatives. However, the purpose is specific enough that an agent can infer it is for changing capacity status, but exclusion conditions are missing.

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