get_setup_summary

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

Explicitly describes as read-only, which is a key behavioral trait. Lists resources included, but does not mention auth requirements (only hinted by access_token param) or potential side effects. With no annotations, this is reasonably transparent.

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?

Single sentence front-loading key information ('full read-only inventory'). No wasted words, efficient and clear.

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 no output schema, description adequately explains what the tool returns (inventory of listed resources) but lacks detail on output structure or format. Sufficient for basic understanding but not fully 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 has one parameter (access_token) with 0% description coverage. Description adds no meaning about this parameter, such as its purpose or requiredness. Agent must infer from context.

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?

Description clearly states it retrieves a full read-only inventory of ExD resources, listing specific resource types (offers, collections, etc.). It distinguishes from sibling tools that focus on individual resource operations.

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?

Implies usage for overview via 'full read-only inventory', but no explicit guidance on when to use this tool versus siblings (e.g., for specific resources) or when not to use it.

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