confluence_get_recently_modified

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

Annotations already declare this as read-only, open-world, and idempotent, so the safety profile is covered. The description adds the 'recently modified' temporal scoping but does not disclose ordering, date-window behavior, or whether results are metadata-only or include content. This is acceptable but limited beyond what annotations provide.

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, front-loaded sentence with no filler or redundant content. It efficiently communicates the core function in five words.

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 read-only list tool with well-documented parameters and strong annotations, the description is minimally sufficient. However, it lacks guidance on result ordering, default limits beyond schema, and how 'recently modified' is defined, and there is no output schema to compensate. This leaves noticeable gaps for an agent deciding between similar list/search tools.

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 parameters, with clear descriptions for 'limit' and 'spaceKey'. The tool description does not add additional parameter context, but it does not need to because the schema already fully documents the parameters.

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 identifies the action ('get') and the resource ('recently modified pages'), which distinguishes it from generic page retrieval tools like 'confluence_get_pages'. It is more specific than a bare title, but it does not explicitly explain how this differs from sibling search or list tools.

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 description provides no guidance on when to choose this tool over alternatives such as 'confluence_get_pages', 'confluence_search_pages', or 'confluence_get_page'. There is no mention of prerequisites, preferred cases, or exclusions, so the agent must rely on the tool name and schema alone.

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