Novedades desde la última revisión

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

Discloses key behaviors: uses fresh data (ignores cache), updates baseline unless save=false. With no annotations, description fully covers behavioral context. Could mention side-effect of baseline update more prominently.

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 front-load the action and provide essential usage guidance. Every sentence contributes value without redundancy.

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 no output schema and one parameter, the description sufficiently defines behavior and return content. Lacks structured output details, but the description is adequate for an agent to form expectations.

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% and the description repeats the schema's description for the 'save' parameter without adding new meaning. Baseline 3 is appropriate.

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 the tool compares current academic status with last review and returns specific changes (new tasks, grades, delivery status, dates). It distinguishes from siblings by focusing on change detection rather than single-purpose retrieval.

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?

Explicitly recommends the tool for answering 'Is there anything new?' and periodic checking. Provides clear context, though does not explicitly mention when to avoid it or alternatives.

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