Get Rfq User Id

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered. The description adds one genuinely new behavioral fact: the call is scoped to the authenticated participant, implying an auth requirement and that the value is identity-derived rather than an input. It says nothing about failure modes when unauthenticated or whether an RFQ account must exist first.

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?

A single well-formed sentence with the key qualifier ('public', 'authenticated participant') front-loaded and no wasted wording. It is arguably too terse for the value it could add, but nothing is redundant.

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 zero-parameter read-only getter with no output schema, the description is adequate but leaves open what the returned ID is used for and whether it is stable across sessions. A brief note on where this ID feeds into the RFQ/quote workflow would make it complete.

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 tool takes zero parameters and the schema is fully described, so there is nothing for the description to clarify beyond confirming the no-argument nature of the call. Baseline 4 applies.

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 uses a specific verb ('Returns') and a precisely named resource ('the public RFQ user ID'), scoped to 'the authenticated participant'. An agent can distinguish it from siblings like get_rfqs or get_quotes, though it never explicitly contrasts itself with them.

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?

There is no guidance on when this tool should be called, what it is a prerequisite for (e.g., identifying oneself when creating or reading RFQs), or any conditions/exclusions. Usage is only inferable from the name and the 'authenticated participant' phrasing.

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