ebay_get_charity_org

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

With readOnlyHint=true already covering the safety profile, the description adds genuinely useful behavior: it requires only an application (client-credentials) token with EBAY_CLIENT_ID/EBAY_CLIENT_SECRET, no user consent, and it documents the two supported marketplaces. This is more than the annotations provide.

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?

Front-loaded with purpose, then return fields, then marketplace constraint, then auth model in a compact form. The field enumeration is slightly list-heavy, but every clause carries information an agent needs for this endpoint.

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 single-resource read with no output schema, the description supplies returned fields, required ID provenance, allowed marketplaces, and the exact credential model. Nothing an agent needs to call this correctly is missing.

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 100%, so both parameters are already fully documented, including the enum and the fact that marketplaceId is sent as the X-EBAY-C-MARKETPLACE-ID header. The description only restates the enum and the charityOrgId provenance, adding no meaning beyond the schema, so the baseline 3 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?

States a specific verb and resource ('get one charitable organization') and explicitly distinguishes itself from the plural sibling by sourcing charityOrgId from ebay_get_charity_orgs. It also enumerates the returned fields, so an agent knows exactly what this retrieves.

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?

Gives clear context: use it to fetch a single org by ID obtained from ebay_get_charity_orgs, and it works only for marketplaceId EBAY_US or EBAY_GB. It does not name an alternative or an explicit when-not condition beyond the marketplace restriction, but the routing to the list tool is implied.

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