get_novedades_expedientes

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

With no annotations, the description carries the full burden. It discloses the 7-day activity filter and the return fields, which is useful. However, it doesn't mention pagination behavior, ordering, or that it returns only summary data. The 'Get' verb implies read-only, but safety traits are not explicitly stated.

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, direct sentence stating the operation, the time filter, and the return fields. There is no redundancy or filler, making it efficient and front-loaded.

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 paginated list tool with high-coverage schema and an output schema, the description covers the essential purpose and returns. It doesn't explicitly note that it returns only a summary or specify ordering, but the current text is sufficient for an agent to correctly invoke the tool.

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?

The input schema has 100% description coverage for both pageSize and pageIndex, so the schema already documents the parameters. The tool description adds no parameter-specific information, only the return fields. This meets the baseline for high schema coverage.

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 uses the specific verb 'Get' and identifies the exact resource: 'expedientes (cases) that had activity in the last 7 days'. It lists return fields (case number, title, court, status, location), distinguishing it from sibling tools like get_novedades_cedulas and get_expediente. This makes the purpose unmistakable.

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?

The temporal filter 'in the last 7 days' provides clear context for when this tool is appropriate. It doesn't explicitly mention alternatives or exclusions (e.g., use get_expediente for full case details), but the 'novedades' (updates) use case is clearly distinct from the other sibling tools.

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