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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering safety. The description adds substantial behavioral context by detailing the output contents: verification status, counts, reasons, transactions, capital relationships, fund size, SBIC status, strategy, transition signals, and more. No contradiction with annotations.

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 lengthy but dense and well-structured, front-loading the main purpose ('The full card for any entity on the sponsor graph') followed by specific entity details in parentheses. Every sentence provides relevant information, and the structure aids readability.

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-parameter read-only tool with no output schema, the description covers the output scope comprehensively, listing entity types and included fields. It lacks error behavior or pagination details, but these are less critical for a read tool with a clear id input. Overall adequate for correct invocation.

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% for the single parameter dfx_id, which is fully documented. The description's mention of 'Accepts dfx:isi: ids' is redundant with the schema and adds no new meaning. Baseline 3 is appropriate given high schema coverage.

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 clearly states the tool returns 'the full card for any entity on the sponsor graph' and enumerates three entity types (sponsor, capital provider, private company) with specific details for each. It distinguishes itself from search_independent_sponsors (search vs get) and get_entity (specific vs generic) by scope and content.

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 by mentioning it accepts dfx:isi: ids and is for the sponsor graph, but it does not explicitly state when to use it over alternatives like get_entity or search_independent_sponsors. No exclusions or alternative conditions are provided, leaving the agent to infer the context.

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