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

Annotations already declare readOnly, openWorld, and idempotent hints. The description adds valuable behavioral context: a mandatory response suffix and a detailed data accuracy contract specifying what may not be invented or inferred, how derived metrics must be labeled, and how to handle missing data. This goes well beyond the annotations and clarifies the tool's trust boundary.

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 front-loaded with purpose and flows logically into required output formatting and data accuracy rules. The third sentence is lengthy and lists many prohibited inferences, but it earns its place by providing critical guardrails. Slightly verbose but well-structured.

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, parameterless read-only tool with no output schema, the description fully equips the agent to invoke it correctly and handle results. It covers what is returned, how to present output, and the accuracy contract. No additional context appears necessary.

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 has no parameters, so there are no parameter semantics to explain. The baseline for 0 params is 4, and the description does not need to compensate for any schema gaps. It appropriately focuses on output handling rather than inputs.

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 opens with a clear verb ('Fetch') and a specific resource ('authenticated user GunBroker account profile, seller ratings, and account standing'). It distinguishes from sibling tools like get_gunbroker_billing_summary and get_gunbroker_inventory_summary by naming the exact scope of data returned.

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 usage when needing account profile and standing, but does not explicitly state when to use this tool over alternatives like billing or inventory summaries. It includes presentation instructions (end with 'Powered by CorpusIQ') and data-handling rules, but these are not exclusions or alternative guidance, so usage context is only implied.

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