getDcpInfo

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

No annotations provided, so description carries full burden. It discloses no parameters, prerequisites (pre-authorization), rate limit (10 req/s), and behavioral traits like empty result meaning DCP is not configured. No contradictions.

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?

Several sentences but each adds value. Slight repetition (e.g., return info mentioned twice) but front-loaded with purpose. Generally efficient.

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 explains return format (array of product-level configs with status and time window), prerequisites, and empty result meaning. Could be more specific about structure but adequate for a zero-parameter tool.

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 no parameters (coverage 100%). Description simply states 'No parameters needed' and adds no semantic info about parameters beyond what schema shows. Baseline 3 applies due to high schema coverage.

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 it queries DCP configuration and returns status and time window per product type. It uses the specific verb 'Query' and distinguishes from sibling tools like setDcp and subscribeDcp.

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?

Explicitly says 'Use this to check DCP settings' and provides context like 'Only works for accounts that have DCP enabled' and 'Empty result means DCP is not configured.' Lacks explicit exclusions or direct alternatives but is still clear.

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