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

Annotations already declare a read-only, non-open-world operation, so the safety profile is covered. The description adds genuinely useful context that no account/auth is required, but says nothing about rate limits, response shape, or whether the returned entry points are live or informational.

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?

Two short clauses with no filler, and the most important content (what the company sells and who it's for) is front-loaded ahead of the auth note. Nothing could be removed without losing 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?

For a zero-parameter read-only lookup with no output schema, the description adequately signals the scope of returned data and the absence of auth requirements. A nod to response format would make it fully self-sufficient, but the gap is small.

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 for the description to clarify beyond confirming that no inputs are required, which the 'no account needed' note reinforces. Baseline 4 applies for a parameterless tool.

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 the resource (company) and enumerates the content returned: what it sells, target audience, and every agent/API entry point. That makes it easy to separate from siblings like list_pricing and search_site, though no explicit verb is used, leaving the operation slightly implied.

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 only guidance is 'No account needed', which tells the agent it can call this without authentication, but there is no statement of when to prefer this over list_pricing or search_site, nor any exclusions or preconditions beyond auth.

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