request_enrichment_v1_enrichment_request__provider___dataset__po

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

With no annotations, the description fully discloses auth method, public nature, rate-limiting, audit logging, conditional queuing, and worker wake. It is transparent about what happens on success and under rate-limiting.

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 well-structured: first line gives core info (method, path, auth, purpose), then two sentences cover rate-limiting and effects. Every sentence adds value and is 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?

The description covers purpose, auth, rate-limiting, and effects, but lacks information about the response/return value. Given no output schema, this is a minor gap; overall it is fairly complete for a simple POST endpoint.

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?

The description does not explicitly define the 'provider' and 'dataset' parameters; it only uses them in the path. Schema coverage is 0%, so some explanation would be beneficial, though the names are somewhat clear 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?

The description clearly states it is for requesting enrichment of a dataset, specifying the HTTP method and path. It distinguishes itself from sibling tools like submit_request by being a public enrichment-specific endpoint.

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 description explains that it is public, authenticated, and rate-limited (one request per user per dataset per hour). It describes the effect (audit logging, queuing, worker wake) and compares to the admin retry endpoint, but does not explicitly mention when not to use it or alternatives.

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