agdp_get_my_jobs

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

The readOnlyHint annotation already marks this as a read operation; the description adds the meaningful constraint that an active wallet is required, which is not captured in the annotations. It does not describe return format or edge cases, but given the safety annotation, this additional context raises it above baseline.

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 concise, using only two sentences to convey both the action and a key prerequisite. It is front-loaded with the primary purpose, and every word contributes to understanding the tool.

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 simple listing tool with one optional parameter and no output schema, the description covers the essential purpose and a critical prerequisite, and the schema handles the parameter. It could be enhanced by mentioning the return type, but the overall context is sufficient given the tool's simplicity.

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 schema fully documents the single 'status' parameter with an enum and description, so the description adds no new parameter semantics. The mention of 'active or completed' mirrors the schema, providing no additional value beyond the structured definition.

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 lists the user's active or completed jobs from the aGDP marketplace, using a specific verb ('List') and resource. This distinguishes it from sibling tools like agdp_get_offerings and erc8183_get_job.

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 implies the tool is for viewing jobs associated with the caller, and notes the wallet requirement, but it doesn't explicitly compare with alternative tools or state when not to use. For example, it doesn't clarify differences from erc8183_get_job or acp_get_job, leaving usage guidance to inference.

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