List company mentions / notifications

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the read-only nature is known. The description aligns with these annotations and adds minimal context by specifying 'admin notifications', but does not disclose additional behavioral traits such as auth requirements or data scope limitations.

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 description is a single, clear sentence with no redundant words. It efficiently states the action and target, making it appropriately concise.

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?

The tool has an output schema, so return values are presumably covered, but the description lacks context on when to use this tool versus personal_read_company_mentions and does not mention pagination or the max_results default. It provides a minimal but adequate overview for a simple list operation.

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 description coverage is 0%, and the description provides no information about company_id or max_results. The parameter names are somewhat self-explanatory, but the description does not compensate for the lack of schema documentation, leaving the agent to infer meanings and defaults.

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 'List admin notifications for the page' uses a specific verb ('List') and resource ('admin notifications'), clearly indicating a read operation. It is distinguishable from sibling tools like personal_read_company_mentions by the company-level focus, though there is slight ambiguity between 'mentions' and 'admin notifications'.

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?

No guidance is provided on when to use this tool versus alternatives. The description does not mention that company_list_mentions should be used for company-level notifications while personal_read_company_mentions handles personal ones, nor does it address any other usage conditions.

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