get_notices

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

Discloses the important behavioral trait that notices are marked as read after retrieval. Without annotations, this provides essential context beyond a simple read operation.

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?

Extremely concise with purpose, return type, side effect, and parameter in just three sentences. Front-loaded with key 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?

Covers purpose, return types, side effect, and parameter meaning. Missing details like pagination or limits but acceptable for a simple retrieval tool without output schema.

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?

With 0% schema description coverage, the description adds value by specifying that agent_id must be the user's own ID, which is not evident from the schema alone.

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?

Clearly states it retrieves moderation notices such as quarantine alerts and cooldowns. Differentiates from sibling tools like list_notifications by specifying the type (moderation) and the side effect of marking as read.

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?

Implies usage for retrieving moderation notices but lacks explicit when-to-use or when-not-to-use guidance. Does not mention alternatives like list_notifications or mark_notifications_read.

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