blackboard_list_institution_announcements

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

Annotations already declare readOnly, idempotent, non-destructive, openWorld. The description adds a key behavioral note: an empty result does not imply a permissions error, which is useful context beyond annotations. It does not cover pagination or rate limits.

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 concise sentences with no filler. Purpose is front-loaded, followed by parameter notes and a behavioral caveat. Structure is efficient though the first sentence is slightly dense.

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 list tool with rich annotations and no output schema, the description covers purpose, optional parameters, and empty-result behavior. However, it lacks explicit sibling routing and detailed parameter semantics, leaving some gaps for an agent.

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 description must explain parameters. It mentions 'título y vencidos opcionales' (title and expired optional), mapping to the two parameters, but does not clarify defaults, matching behavior, or exact meaning of includeExpired.

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?

States it lists institutional announcements within Aula Virtual UP, differentiating by scope from course-level siblings via 'institucionales'. However, it does not explicitly name alternatives like blackboard_list_announcements, so sibling differentiation is 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?

Mentions optional title and expired filters and warns that an empty result is not a permissions error, which helps interpret output. But it gives no guidance on when to choose this over other announcement tools such as search_announcements or list_announcements.

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