codecks-mcp

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

With no annotations, the description carries full burden but only states it generates a summary. It doesn't disclose behavioral traits such as whether it's read-only, requires authentication, has rate limits, or what the output format is. This leaves significant gaps in understanding how the tool behaves beyond its basic function.

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, efficient sentence that front-loads the purpose. It avoids unnecessary words, but could be more structured by explicitly mentioning parameters or output, though it's appropriately sized for the tool's apparent simplicity.

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 annotations, no output schema, and low schema coverage (33%), the description is incomplete. It doesn't explain return values, error handling, or how parameters interact, making it inadequate for a tool with 3 parameters and potential complexity in generating summaries.

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 description coverage is 33% (only 'days' has a description), so the description must compensate but doesn't add meaning for 'project' or 'owner'. It implies parameters relate to filtering (e.g., 'recently done cards'), but doesn't explain their roles beyond what's minimally inferred, resulting in a baseline score due to partial 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 states the tool generates a 'daily standup summary' with categories like 'recently done, in-progress, blocked, and hand', which gives a vague purpose. It specifies the type of output but doesn't clearly distinguish what resource it operates on (e.g., cards, projects) or how it differs from sibling tools like list_cards or list_activity, making it somewhat ambiguous.

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?

No explicit guidance on when to use this tool versus alternatives is provided. The description implies it's for daily summaries, but it doesn't specify prerequisites, context (e.g., for project management), or when not to use it, leaving the agent with minimal direction.

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