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

Annotations already declare read-only, idempotent, and closed-world, so the safety profile is covered. The description adds genuinely non-derivable context: a personal access token created by the account owner, a free-trial-or-paid plan requirement, and that only that account's data is read — plus the 365-day reminder interval that defines one of the categories.

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 purpose and the four qualifying conditions are front-loaded in the first sentence, with auth and plan prerequisites trailing. The enumeration is long but each item earns its place as a distinct trigger; the sentence is dense enough to require a careful read.

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 zero-parameter read tool with no output schema, the definition covers what is returned (each item carries a link), who may call it (token and plan), and the scope of data. Pagination and response volume for large inventories are left unstated, which is the main remaining gap.

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 no parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. It correctly avoids inventing filter options that the empty schema does not support.

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 names a specific resource (safety data sheets in the caller's own SDSentry inventory) and enumerates the four exact conditions that qualify a sheet, which goes well beyond restating the title. It never names a sibling tool, so an agent must infer the boundary against find_sds_for_inventory or check_hazcom_readiness on its own.

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 enumerated triggers (file changed, not reviewed in 365 days, text missing product name, no SDS on file) make the intended use clear in context, and the phrase 'your own inventory' scopes it. There is no explicit when-not guidance and no routing to alternatives among the nine sibling tools.

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