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

Adds key behavioral details: never returns full article text, data source (AI Law Tracker, CC BY 4.0), informational only disclaimer. Aligns with annotations (readOnlyHint, etc.).

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 well-structured sentences covering returned fields, access tiers, licensing, and disclaimer. No wordiness, front-loaded with core action.

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?

Provides sufficient context for a news listing tool with 8 parameters and no output schema. Covers access limitations, data source, and disclaimer. Lacks detail on pagination or query syntax, but schema partially covers.

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 100% with individual parameter descriptions. The tool description adds overall context but does not enhance individual parameter understanding beyond schema.

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?

Description clearly states it lists audited AI-regulation news headlines with specific fields (headline, excerpt, publisher, source URL) and distinguishes from sibling tools like list_ai_laws or get_ai_law by focusing on news feed.

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?

Describes access tiers (free/anon vs Developer+) and the data scope, but does not explicitly guide when to use this tool over siblings like list_law_feed or search_ai_laws.

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