monday-dev: Get Sprint Summary

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

Annotations already indicate read-only and idempotent. Description adds constraints (must be completed) and output format details (user IDs), adding value beyond annotations without contradiction.

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?

Well-structured with sections (Purpose, Requirements, Important Note) and bulleted content. No unnecessary sentences, though slightly long. Front-loads the core purpose.

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?

Covers the return content, prerequisites, and a usage hint. No output schema, so description sufficiently explains what to expect. Could detail output format more but adequate for agent use.

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?

Input schema already describes sprintId (100% coverage). Description adds valid value constraints (completed sprint, after 1/1/2025), improving parameter understanding beyond schema.

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?

Clearly states 'Get the complete summary and analysis of a sprint' and lists specific content categories (scope, velocity, etc.). However, it does not explicitly differentiate from sibling tool get_sprints_metadata.

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?

Provides prerequisite (sprint must be completed, created after 1/1/2025) and a useful note on handling user IDs with list_users_and_teams. Lacks explicit when-not-to-use or alternatives but gives clear context.

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