Sellers_getAccount

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

No annotations are provided, so the description carries the behavioral disclosure burden. It does communicate that the tool is a read operation ('Returns information') and that execution happens externally in the Kuudo deployment. However, it does not mention authentication requirements, side-effect potential, rate limits, or the implications of 'not here' for the calling agent.

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 short and the key behavioral information is front-loaded in the second sentence. 'Catalog entry' is a somewhat vague prefix that does not earn its place, but overall the description is compact and readable.

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?

There is no output schema and no annotations, so the description should explain what the returned 'information about a seller account and its marketplaces' actually contains. The term 'information' is vague—an agent cannot predict the response shape, included fields, or how marketplaces are represented. The unexplained 'Kuudo deployment' reference also leaves a gap in understanding the invocation context.

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 input schema is empty with zero required parameters, so there are no parameter semantics to document. Schema description coverage is 100%, and the description correctly says nothing about parameters. With zero params, a high baseline score is appropriate.

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 clear verb and object: 'Returns information about a seller account and its marketplaces.' This distinguishes it from Sellers_getMarketplaceParticipations, which focuses on marketplace participations only. The phrase 'Catalog entry' is confusing and adds noise, but the core purpose is 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?

There is no guidance on when to choose this tool over Sellers_getMarketplaceParticipations or SellerWallet_getAccount. The only context added is 'Runs in your Kuudo deployment, not here,' which describes the execution environment but does not help an agent decide when this tool is appropriate or when an alternative should be used.

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