list_schema_fieldgroups

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

With no annotations provided, the description carries the full burden for behavioral disclosure. It only states 'Read-only,' which is a single behavioral trait. It does not disclose auth requirements, pagination behavior, rate limits, or any side effects, which are important for a list operation.

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 of 10 words, which is very concise. However, it may be under-specified, trading completeness for brevity. Nonetheless, it is well-structured and front-loaded.

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 low complexity (2 params, no output schema, no annotations), the description is incomplete. It fails to explain the return format, possible pagination, what 'compatible with the Offer Item class' means, or how to interpret results. The agent lacks sufficient context to use the tool effectively without external knowledge.

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 tool description does not explain any parameter semantics. The two parameters ('access_token' and 'include_global') are not described, leaving the agent without guidance on what they do or how to use them.

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 action ('List') and resource ('all tenant fieldgroups') with a constraint ('compatible with the Offer Item class'). It also notes it is read-only. However, it does not explicitly differentiate from sibling tools like 'get_fieldgroup' or 'create_offer_metadata_fieldgroup', but the purpose is sufficiently clear.

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 guidance on when to use this tool vs. alternatives. It does not mention prerequisites, exclusions, or context for when to choose this over similar tools like 'list_schema_descriptors' or 'get_fieldgroup'.

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