search_entra_news

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

No annotations provided, so description bears full burden. Discloses date range (mid-2023 to present), hybrid search dependency on OPENAI_API_KEY, and return fields. Lacks details on pagination, error handling, or empty query behavior.

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?

Three sentences, front-loaded with core action, no filler. Efficiently covers purpose, date range, and search modes.

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?

Adequately describes input, date range, search modes, and output nature for a search tool with no output schema. Could mention result ordering or more on hybrid search behavior.

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 100%, so baseline 3. Description adds valuable context: query is versatile, limit default and max, mode enum with hybrid as default and semantic requiring API key.

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 searches the full Entra.news archive using natural language or keywords, returning sourced excerpts with issue number, date, and URL. Distinct from siblings like get_issue (single issue) and list_issues (list issues).

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?

Provides context on search modes and API key requirement for semantic search, but does not explicitly guide when to use this vs. alternatives like get_issue or find_tool_mentions.

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