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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety bar is low. The description adds genuinely new behavioral context: every fact carries a source and the About page URL is included, telling the agent the data is attributed and static rather than user-generated.

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?

A single front-loaded sentence: the core claim comes first, then the field inventory. No preamble, no restatement of the title, and every clause tells the agent something it can use.

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 an output schema present, return-value detail is not required, and with zero parameters there is nothing else to specify. Fields, provenance and the About URL are all covered; nothing an agent needs in order 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?

Zero parameters, so per the baseline this scores 4. The description correctly implies a call with no arguments and spends no words on nonexistent parameters.

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?

A specific verb ('Returns') plus resource ('public facts about ProfitDrawer') with an enumerated field list including description, website, founding year, currency and social profiles. The resource is clearly distinct from the sibling calculators and list/query tools, though the description never explicitly distinguishes it from search_profitdrawer, the closest neighbor.

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?

Usage is only implied: the field list hints at answering 'who/what is ProfitDrawer' questions. There is no explicit when-to-use statement, no exclusion of search_profitdrawer or get_answer for the same questions, and no mention that no arguments are required.

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