Get My Open Items Statistics

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

Annotations already provide readOnlyHint=true, destructiveHint=false, and idempotentHint=true. The description adds that the response is paginated and includes pagination metadata, which is useful but not extensive. It does not disclose any side effects beyond what annotations imply. No contradiction with annotations.

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 5 sentences but includes redundant information (e.g., 'Required parameters: project_id' ) and a contradictory statement. The first two sentences conflict, making it less concise.

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 the complexity of the tool (name implies statistics, description implies listing), the description is incomplete. It does not clarify the discrepancy, and there is no output schema to specify the return structure. Pagination details are provided but not enough to fully understand 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 description coverage is 100%, so baseline is 3. The description reiterates that project_id is required (already in schema) and mentions pagination but does not explain the tool_name enum values or how they affect the output.

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 'Return open items statistics for a project (current user)', which is a clear verb+resource, but then contradicts by saying 'fetch the full details of a specific Project-Level Configuration records' and 'Returns a paginated JSON array of Project-Level Configuration records', which suggests this is a listing tool rather than a statistics endpoint. This creates ambiguity about the tool's actual purpose.

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 does not provide any guidance on when to use this tool versus its siblings, such as get_open_items_statistics or other tools. It mentions 'Use this to fetch...', but this is generic and does not differentiate from alternatives.

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