signupgenius_report_filled

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds auth requirements, session-mode restriction, and scope limitation to the key-holder's own sheets, which are behavioral constraints beyond the annotation. It does not detail the report's output structure or pagination, but those are not critical given the tool's simplicity.

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 front-loads the purpose, the second packs constraints and the alternative. Every clause earns its place with no redundancy or filler.

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 report tool, the description covers auth, scope, and the key sibling alternative. It does not explicitly describe the report's return format, but given the absence of an output schema and the tool's clear purpose, this is a minor gap. The guidance to use list_slots for availability is a strong addition.

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 only parameter signupId has a schema description ('Sign-up ID (signupid).'), providing 100% coverage. The tool description does not add any extra meaning about the parameter beyond what the schema already states, so the baseline 3 applies.

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 the tool produces a report for a sign-up, specifically restricted to already-filled slots. The phrase 'restricted to slots that have already been filled' distinguishes it from report_all and report_available, and the mention of list_slots as an alternative further differentiates its 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 explicitly lists prerequisites (SIGNUPGENIUS_USER_KEY, Pro subscription, session mode not supported, only sheets the key-holder created) and names the alternative signupgenius_list_slots with the condition 'prefer ... on ANY sign-up (including sheets the user did not create)' and notes it needs no auth. This gives clear when-to-use and when-not-to-use guidance.

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