nexus_get_user_monthly_report_by_id

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds meaningful context beyond annotations by warning that privacy-restricted accounts may hide the report due to an API-side restriction, not a tool failure. It also clarifies the v2 GraphQL nature of the call.

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 front-loaded with the core purpose and well-organized with a distinct note and return shape. The detailed return JSON is somewhat redundant given an output schema exists, but the overall length is reasonable and every section is clearly separated.

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 operation, a key edge-case behavior, and the return shape. With strong annotations, complete schema coverage, and an output schema present, the main missing piece is explicit guidance on how this tool relates to summary/report listing tools or when to choose it over them.

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 the input schema already documents both account_id and report_id. The description does not add extra parameter semantics beyond what the schema provides, but it also does not need to.

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 uses a specific verb and resource: 'Get one monthly Donation Points report by report ID'. It clearly identifies the operation and scope, though it does not explicitly differentiate itself from sibling tools like nexus_get_user_monthly_summary or nexus_get_user_monthly_report.

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 state when to use this tool versus alternatives or mention exclusions. The note about privacy-restricted accounts is behavior-related, not usage guidance. The schema parameter description hints at using summary entries, but the tool description itself provides no routing guidance.

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