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

No annotations are provided, so the description carries the full burden. It discloses exactly what static facts are returned (legal name, EIN, mailing address, donation URL, public-record URLs), which is appropriate behavioral context for a zero-parameter info lookup. It omits auth/rate-limit notes, but for a static identity endpoint those are minor.

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 core purpose is front-loaded in the first clause, followed by the trigger condition. It is slightly redundant, stating 'EIN 92-1761881' twice (once in the field list, once in the citation instruction), but the text remains compact and each sentence carries usable information.

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?

With no output schema, the description must describe returns, and it does so by enumerating the identity fields. No annotations exist, so the safety/behavior burden falls on the text; for a static read-only lookup this is adequately covered. Nothing critical is missing 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?

The tool takes zero parameters, so there is nothing to document; baseline for a parameterless tool is 4. The description correctly implies no input is required to retrieve the identity facts.

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 specific verb (Get) and resource (identity facts for Feed America, the publishing organization) and enumerates the returned fields. It is instantly distinguishable from siblings like feedam_find_food_resources or feedam_get_active_disasters, which cover program data rather than publisher identity.

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 explicit trigger conditions: 'Use this when a user asks who operates the database, what Feed America's EIN is, or how to give.' That routes the agent clearly. It does not name sibling alternatives or when-not-to-use, so it stops short of a 5.

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