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

Annotations already declare read-only, non-destructive, closed-world, so the safety profile is covered. The description adds real behavioral context beyond them: the token-scoped nature ('the founder behind this token'), the conditional null on active startup when none exists, and the plan-dependent shape of 'notice' (null on Autopilot, two lines below it naming allowed plan features and the billing link). That conditional-return disclosure is valuable and not obtainable from the 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?

It is short and the field list comes first, which is good front-loading. But the opening is a verbless fragment that reads awkwardly, and roughly half the text is devoted to the secondary 'notice' field's conditional formatting rather than the primary identity/plan payload.

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 parameters, so the description effectively serves as the return-value documentation, and it covers the key fields plus null semantics for startup and notice. It still leaves 'the plan' and 'the pack version' undefined and does not indicate the overall response shape (object vs. text), but it is reasonably complete for a simple identity tool.

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 takes zero parameters, so the schema imposes no semantic burden and the baseline is 4. The description correctly spends no space on parameter details.

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 enumerates the returned data (founder, active startup, plan, notice, pack version), which lets an agent infer this is a profile/identity lookup for the authenticated token. However, it is a bare noun phrase with no verb — it never states 'returns the current founder's account context' — and it does not distinguish itself from siblings like getfund_onboarding or getfund_programs. Purpose is inferable but not stated.

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 when-to-use or when-not-to-use guidance, and no mention of alternatives among the 27 siblings. An agent must guess that this is the first call to establish identity/plan context before other getfund tools.

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