Get Open Items Statistics

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

The annotations already indicate readOnlyHint=true, so the description adds minimal behavioral insight. It mentions pagination and metadata but contradicts itself regarding the return type (statistics vs. full records). This inconsistency undermines transparency about what the tool actually returns.

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 contains redundant and conflicting information (e.g., separate mentions of statistics and configuration records). It is not concise and could be streamlined to a single coherent purpose statement.

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?

With 4 parameters and no output schema, the description needs to clarify the return format. It claims a paginated JSON array of 'Project-Level Configuration records,' but the tool name suggests statistics, not records. This incomplete and misleading explanation fails to equip the agent with a clear understanding of the tool's behavior.

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 coverage is 100%, so the baseline is 3. The description adds a brief reminder about pagination control (page, per_page) and labels project_id as required, but does not provide additional semantic meaning beyond what the schema already offers.

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 begins by stating it returns "open items statistics" but then contradicts itself by saying it fetches "full details of a specific Project-Level Configuration records." This duality creates confusion about whether the tool returns summary statistics or detailed records, making its primary purpose unclear.

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 over alternatives like get_my_open_items_statistics (which filters by user). The description does not specify suitable contexts or explicitly exclude cases where the sibling tools would be more appropriate.

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