list_schema_descriptors

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

With no annotations provided, the description carries the burden. It states 'Read-only', which is a key behavioral trait. However, it does not disclose authentication requirements, rate limits, pagination behavior, or what happens if access_token is missing. For a simple list tool, this is minimally sufficient.

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—just two short statements. Every word serves a purpose. However, it could be slightly more structured by explaining parameters. No wasted text.

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's simplicity (list operation, single optional param, no output schema), the description covers the basic purpose and read-only nature. But it lacks details on return format, pagination, or how to interpret results. 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 description coverage is 0% and the description fails to mention the single parameter 'access_token' at all. The agent receives no guidance on what this parameter is for, its format, or necessity. This is a significant gap.

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 clearly states the verb 'List', the resource 'descriptors on the decisioning schema', and enumerates specific descriptor types (identity, deprecation, display name overrides, relationships). It also adds 'Read-only' to indicate safety. This distinguishes it from sibling tools like list_offer_items or list_schema_fieldgroups.

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 explicit guidance on when or when not to use this tool. The description implies use for viewing schema descriptors but does not compare to alternatives or mention prerequisites. This is adequate but lacks deeper context.

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