regdata_run_result

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

No annotations provided, but description fully discloses behavior: returns dataset items when finished, returns same handle if still running, mentions billing implications and waitSecs policy.

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?

Three well-structured sentences with no wasted words. Front-loaded with purpose, each sentence adds critical information for agent use.

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 behavior ('dataset items' or 'same handle') adequately. Parameter descriptions are complete. Could mention status codes or error handling, but sufficient for tool use.

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 coverage is 100%, so baseline is 3. Description adds context: runId is from a pending call, maxItems is optional cap, waitSecs includes range and default. This adds value beyond schema descriptions.

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 collects the result of a running regdata check, specifying verb ('collect') and resource ('result of a regdata check'). It distinguishes from siblings by explaining the polling pattern and avoiding double-charging.

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 tells when to use: when any regdata tool returns {status, runId, note} instead of results. Warns not to re-run the check to avoid double charge, and instructs to call with the runId.

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