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 profile is covered. The description adds that results carry fact ids, statuses, dates and source pages (provenance) and that no topic returns anything outside the fact book, but with an output schema present the return-shape detail is partly redundant.

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?

Front-loaded with the core verb and payload, and every clause carries information. It is a single heavily nested sentence with stacked parentheticals and URLs, which costs some readability but wastes no words.

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 optional enum parameter with a fully described schema, an output schema, and non-destructive annotations, this is close to complete: default, disambiguation purpose, and topic scope are all covered. Only the boundary against ask_emergent/search_facts remains unstated.

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 coverage is 100% and the enum is fully documented, so the baseline is 3; the description earns an extra point by explaining what 'disambiguation' actually resolves (emergent.sh and the Austin company at emergenttechnologies.com) and confirming overview as the default when topic is omitted.

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 and resource: returns who Emergent Technologies, Inc. is, what it does, for whom, sourced from its fact book, and delineates itself from the sibling fact-query tools by returning provenance (fact ids, statuses, dates, source pages) plus persona-specific next steps. An agent can tell what it will get without opening the schema.

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?

Gives clear selection logic for the topic parameter: overview is the default, disambiguation is for confusing this company with emergent.sh or the Austin firm, and any other value maps to a fact-book topic. It stops short of stating when to prefer ask_emergent or search_facts instead, so routing versus siblings is left implicit.

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