dealdesk.discover

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

With no annotations, the description carries the full burden. It does disclose the important non-obvious trait that this call unlocks skill-gated tools, which is real behavioral value beyond the name. It does not say whether the unlock persists across sessions, what permissions are required, or that projectId must match the API key's project.

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?

A single compact sentence with no filler, front-loading the listing behavior before the unlock mode. Slightly dense for two distinct behaviors but nothing is wasted.

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?

For a two-parameter meta-tool with no output schema and no annotations, the description covers both invocation modes adequately. It leaves open what the returned domain/tool list looks like and what 'skill-gated' entails, which is where an agent would most likely stumble.

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 100%, so the baseline is 3. The description restates only six of the eight enum values (omitting portfolio-authoring and export), which is a minor mismatch, but it does usefully convey that domain is optional and that omission lists domains only.

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 states a concrete verb and resource: listing DealDesk tool domains, with a secondary mode that unlocks skill-gated tools for one domain. It is distinguishable from CRUD siblings, but it does not explicitly differentiate itself from dealdesk.list_skills, which sounds closely related, and the word 'additional' is left unexplained.

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?

The two modes are implied (list domains vs. unlock a domain), and the schema's 'Omit to list domains only' clarifies the branch. However, there is no statement of when an agent needs discovery at all, no sequencing guidance relative to list_skills, and no mention of prerequisites beyond projectId.

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