Get Dashboard Announcements

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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It only states the return type (announcements) but does not mention whether the result is paginated, if there are rate limits, authorization requirements, or how the parameters affect behavior. This is insufficient for an agent to understand the tool's side effects or constraints.

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 sentence, which is concise, but it sacrifices necessary details. It is front-loaded but too sparse. An additional sentence on parameters or usage would improve structure without losing conciseness.

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?

Given the tool's simplicity (2 optional parameters) and the presence of an output schema, the description need not explain return values. However, it still lacks coverage of parameter semantics and usage guidelines. The description is incomplete for an agent to use the tool effectively without extra knowledge.

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%, so the description must explain parameter meanings. It does not mention 'limit' or 'include_full_text' at all. The agent cannot infer from the description alone what these parameters control, making it difficult to choose appropriate values.

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 clearly states it returns announcements from the Ninova dashboard's aggregated announcements page. The verb 'return' and resource specification are appropriate. However, it does not explicitly differentiate from the sibling tool 'get_course_announcements', which likely returns announcements for a specific course, so the purpose is clear but could be improved with explicit distinction.

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. Given the sibling 'get_course_announcements', an explicit note about scope (aggregated vs per-course) would help the agent choose correctly. The description lacks any usage context or prerequisites.

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