Get one Commertize sponsor

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

Annotations cover only readOnlyHint and openWorldHint; the description adds substantial behavioral context beyond them — that the endpoint is authenticated, that prior deals, realized returns, AUM, principals and verification status are unavailable, and that absences are stated explicitly rather than omitted. It also discloses the informational, non-solicitation nature of the data.

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 content is front-loaded with the core scope and the key caveat before the ancillary disclaimers. It is dense but each clause carries distinct information; the final sentence is a boilerplate disclaimer that earns slightly less than the rest.

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?

Even though an output schema exists, the description usefully sets expectations about what the response contains and, unusually, what it deliberately declares absent. Combined with the single-parameter schema, an agent has everything needed to call it correctly and interpret the result.

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% and the schema already documents both the exact-id and case-insensitive-substring forms, so the description's 'by id or by name substring' is essentially a restatement. It adds no syntax or matching-behavior detail beyond the schema, so the baseline of 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+resource ('One sponsor's public record') and enumerates what the record contains (offerings by status, asset class, geography). It clearly distinguishes itself from list_sponsors and get_offering by scoping to a single sponsor and by the explicit 'NOT A TRACK RECORD' framing.

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?

It gives clear context on the lookup key ('by id or by name substring') and an explicit when-not ('NOT A TRACK RECORD') tied to the authenticated endpoint's limits. It does not, however, route the agent to specific siblings such as list_sponsors or search_offerings when a lookup fails or when multiple sponsors are needed.

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