pipedrive_recently_updated

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

No annotations are provided, leaving the description to disclose behavior. It describes a read operation ('Show'), but does not explicitly state it is read-only, safe, or mention any side effects or authorization needs. With no annotations, the description should be more explicit.

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 wasted words. It conveys the core functionality efficiently.

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?

The tool has 5 parameters and no output schema. The description covers the main idea and two parameters but omits pagination details (cursor, limit). For a list tool, pagination is important context, making the description incomplete.

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 schema has 20% description coverage. The description adds meaning for 'days' and 'as_user' but does not explain 'cursor' or 'limit' for pagination. It partially compensates for the schema gaps but is not comprehensive.

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 shows deals, persons, or organizations updated in the last N days. It uses a specific verb ('Show') and resource, which distinguishes it from sibling tools like pipedrive_deals_list or pipedrive_persons_list that typically return full lists.

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 implies when to use (recent updates) and mentions optional user filter, but does not explicitly state when not to use or name alternative tools. However, the purpose is clear enough for an agent to infer usage context.

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