check_payment_consent_status

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

Annotations already declare readOnlyHint=true, so the agent knows this is a safe read operation. The description adds the return value ('current status') and the context of an 'exact payment consent journey,' but doesn't disclose additional behavioral details like error conditions or rate limits. This is acceptable given the simplicity of a read-only status check.

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 and well-structured with Args and Returns sections. It front-loads the purpose and then lists params and return value. No wasted words, and every sentence earns its place.

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 the tool's simplicity (3 simple params, no nested objects, read-only, output schema exists), the description is fairly complete. It explains what the tool does, the inputs, and the return value. However, it misses a note on how this relates to sibling tools (e.g., when to use payment consent status vs generic consent status), which is a minor completeness gap.

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 0%, and the description compensates by explaining each parameter: subject_id as payer's CPF or internal ID, bank as participating bank identifier, consent_id as the exact payment consent journey to query. This provides meaningful semantics beyond the bare schema. The inclusion of ctx is extraneous but not harmful.

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 'Checks the current status of an exact payment consent journey,' which is a specific verb+resource. It distinguishes itself from the sibling check_consent_status by adding 'payment consent' and 'exact journey,' making the purpose unambiguous.

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?

No guidance is given on when to use this tool versus the sibling check_consent_status or other payment consent tools. The description only implies it's for querying a specific consent journey but does not state exclusions or alternatives.

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