get_creation_activity

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

No annotations are provided, so the description carries the full burden. It does not explicitly state that the tool is read-only or non-destructive. The phrase 'Report' implies no side effects, but this is not confirmed. The description lacks behavioral context.

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 concise, with a clear one-line purpose followed by a parameter list. Every sentence provides value, no fluff. The structure is front-loaded and easy to parse.

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 description covers the basic purpose and parameters. However, it mentions 'quality indicators' without definition or detail. An output schema exists (not shown) which may explain return values, so the gap is partially mitigated. For a moderate complexity tool, this is adequate but not complete.

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 0%, requiring the description to add meaning. It explains each parameter: 'project' is required, 'since' is duration or date with default 7d, 'creator' is optional filter, 'limit' is max issues default 20, 'instance' is optional YouTrack instance. This adds significant context beyond schema titles and defaults.

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 provides a 'Report of recently created issues with quality indicators.' The verb 'Report' and resource 'created issues' are specific. It distinguishes from siblings like 'search_issues' or 'get_issues' by focusing on creation activity with quality indicators.

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 guidance is provided on when to use this tool versus alternatives such as 'search_issues', 'get_issues', or 'poll_changes'. The description does not mention use cases or exclusions.

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