nexus_get_user_monthly_summary

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

Annotations already establish read-only and idempotent behavior. The description adds valuable context beyond annotations by disclosing that it uses v2 GraphQL without consuming v1 REST quota and by specifying the exact return shape. This is useful behavioral detail not otherwise available.

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 and well-structured: a one-line purpose, a short contextual note about API versioning and rate limits, and a compact return shape. Every sentence serves a distinct purpose without redundancy or fluff.

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?

For a single-parameter read-only listing tool, the description fully covers purpose, usage, backend behavior, rate-limit implications, and the return format. It even names the related follow-up tool, making it complete for agent decision-making and invocation.

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?

The input schema already fully describes the single account_id parameter with type, minimum, and description, so the description adds no additional parameter-level semantics. The description does relate the output to userId, which is a minor extra, but the schema carries the parameter documentation burden.

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 a specific verb ('List') and resource ('months a user has a monthly activity report for'), and explicitly differentiates itself from the detailed report tool by noting the follow-up for download/upload numbers. This makes the tool's purpose unmistakable and clearly distinct from sibling tools.

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 gives explicit usage context: use this to list available months, then follow up with nexus_get_user_monthly_report for specific monthly numbers. It also notes the v2 GraphQL backend and its rate-limit behavior, which helps the agent decide when this tool is preferable.

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