lookup_decisioning_schema

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

No annotations provided. The description adds 'Read-only', which clarifies safety but lacks details on authentication, rate limits, or response behavior. Minimal transparency beyond the functional scope.

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 concise sentences with no wasted words. Front-loaded with the core function, followed by specifics about the schema contents.

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?

No output schema and sparse parameter documentation. The description does not cover return format, error conditions, or the effect of the include_deprecated flag. Incomplete for a tool with two parameters that affect behavior.

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%. The description does not explain the two parameters (access_token, include_deprecated) or their purpose. Without this, the agent cannot infer parameter usage from the description.

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 tool fetches the full resolved Personalized Offer Items decisioning schema, listing components (all fieldgroups, OOB fields, custom tenant fields) and labels it 'Read-only'. This distinguishes it from sibling tools that modify schema.

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 to use this tool vs. alternatives. The description implies it's for reading, but doesn't mention when not to use it or suggest sibling tools like get_fieldgroup or list_schema_fieldgroups for partial lookups.

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