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

Annotations already declare this is a non-read-only, non-idempotent, non-destructive write with no open-world access. The description adds the one trait annotations cannot express: 'We read every request' signals human review, asynchronous handling, and no immediate fulfillment. It stops short of saying what the caller receives back or whether duplicate requests are merged, which matters given idempotentHint=false.

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 sentences, no filler, and the core action is stated first with the qualifying condition immediately after. The example list is compact and earns its space by covering the enum surface.

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 simple one-required-field submission tool with no output schema, the description covers what is being asked and that a human will read it. What is missing is any statement of outcome or timing for the caller, which an agent needs in order to tell the user what happens next.

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 50%: topic and contact are documented, while kind and details are not. The parenthetical '(news on a topic, alerts, a ticker, a company, or a data feed)' loosely maps onto the kind enum but mostly restates it, and the details parameter gets no explanation at all in either the schema or the description.

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 gives a specific verb and resource: submit a coverage request to AgentMaverick News for content not currently offered, with examples (topic, alerts, ticker, company, data feed). It is clearly distinct from retrieval siblings like search_news or latest_news, but it never names the closest alternative, subscribe_alerts, so the boundary between 'request new coverage' and 'subscribe to existing alerts' is left implicit.

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?

'something your user needs that we don't cover yet' supplies a real when-to-use condition, which is more than most definitions offer. However, the agent is given no way to determine what is already covered (no pointer to search_news or site_stats), and there is no explicit exclusion such as 'do not use this to subscribe to an existing alert'.

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