get_resumo_semana

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

No annotations exist, so the description carries the full burden. It does disclose the payload sections the tool returns (agenda, open tasks, news, frequency alerts), which is useful behavioral context, but it says nothing about permissions, ordering, volume/truncation, or whether results are cached.

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?

Front-loaded with the return contents and one short args note; no filler. The line-wrapped formatting of the Args block is slightly awkward for a one-parameter tool but harmless.

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 one-parameter, no-output-schema aggregate tool, the description lists what each result section contains, which is the key missing piece an agent needs. It falls short only on how the sections relate to the granular sibling tools and on any pagination or size limits.

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 0% — the schema only gives a type and default for 'dias'. The description supplies the meaning ('tamanho da janela em dias') and confirms the default of 7, which is exactly what the schema omits. It could still clarify whether the window starts today.

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 names a specific aggregate: agenda (exams/tasks), open unsent tasks, recent class news, and attendance alerts over an upcoming window. That distinguishes it from the granular siblings (get_agenda, get_tarefas, get_noticias, get_alertas_frequencia), though it never explicitly says it bundles them.

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?

Usage is only implied: the composite nature suggests it replaces several individual calls for a forward-looking overview, but there is no explicit 'use this instead of X' or when-not guidance. An agent must infer the routing itself.

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