signupgenius_report_all

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

Annotations already declare readOnlyHint=true, and the description goes beyond that by detailing what the report contains (every slot, participant, custom-question answers) and disclosing authentication requirements (Pro key, no session mode). This adds substantial behavioral context without contradicting the 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 two sentences: the first delivers the core purpose, the second adds critical authentication requirements. Both sentences are information-dense with no filler, and the most important information is front-loaded.

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?

Despite lacking an output schema, the description clearly explains what the report returns (every slot, participant, custom answers) and the necessary conditions for use (Pro key, no session mode). Given the tool's read-only nature and the presence of sibling tools for filtered reports, this description is complete enough for an agent to select and invoke it correctly.

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?

There is only one parameter (signupId) and the schema description covers it fully with 'Sign-up ID (signupid).' The tool description adds no additional parameter semantics, but with 100% schema coverage, a baseline of 3 is appropriate.

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 'Full report for a sign-up: every slot plus the participant who claimed it', which specifies the tool's exact purpose and scope. It distinguishes itself from sibling tools like signupgenius_report_available and signupgenius_report_filled by covering every slot, not just a subset.

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 provides clear context: it requires SIGNUPGENIUS_USER_KEY and a Pro subscription, and explicitly notes that session mode is not supported for reports. However, it does not explicitly compare with alternative report tools or state when to prefer this over report_available or report_filled, so it lacks explicit exclusion guidance.

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