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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, which cover the core behavioral safety. The description adds contextual detail ('verified public', 'Base USDC') but does not disclose additional behavioral traits such as return format, error handling, or authentication requirements. With annotations present, the description adds moderate value but not extensive transparency.

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 a single, efficient sentence that front-loads the action ('Read') and delivers all necessary information without fluff. Every word adds value, and it is immediately scannable for an agent.

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 get tool with one parameter and no output schema, the description provides sufficient context for an agent to understand its purpose. It clearly states what is read and for which task type. The absence of return-format details is acceptable since a receipt read is intuitively a receipt object, and the annotations cover safety. Minor gaps like error conditions are not critical for this simplicity level.

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 has one parameter, task_id, with 0% description coverage. The description's mention of 'paid native task' links the parameter to the task concept, adding some meaning beyond the raw regex pattern. However, it does not explicitly define task_id or explain its format, relying on the pattern for that. Given the simplicity of the parameter, the description partially compensates but not fully.

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 specific verb ('Read'), a precise resource ('verified public Base USDC settlement receipt'), and a clear context ('for a paid native task'). It uniquely identifies this tool among siblings like get_job or get_posting_instructions, which serve different purposes. No ambiguity or tautology.

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 used when a settlement receipt for a paid native task is needed, but it does not explicitly mention when not to use it or name any alternatives. There is no contrast with sibling tools, so an agent must infer the appropriate usage context. This is implied usage rather than explicit guidance.

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