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

Annotations already declare readOnly/idempotent/non-destructive, and the description layers on genuinely non-obvious behavior: it returns links only, causes no side effects, enforces a 3-requests-per-24-hours limit, and requires the subject's consent before the email is sent. Rate limits and consent requirements are exactly the kind of context annotations cannot express, so this adds real value beyond structured fields.

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?

Four short sentences, front-loaded with purpose and then the constraint/consent rule. The 'only returns links / sends nothing / creates nothing' pair is deliberately redundant for emphasis and earns its place by forestalling a wrong write-action inference.

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 one-optional-param read tool with an output schema, everything the agent needs is present: scope, side-effect absence, rate limit, consent requirement, and the pre-call check order. Return values need not be described since an output schema exists. Nothing material is missing.

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% and the single `email` parameter is already documented as optional with its effect on the response ('how many free brief requests it has left today'). The description mostly restates that the email is used to check the limit and adds a consent qualifier, which is helpful but marginal. Baseline 3 applies when the schema does the heavy lifting.

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?

Specific verb+resource ("Gets the debriefing.io links" for free brief requests, workspace signup, plan comparison) with the exact scenario boundaries stated. It implicitly but clearly separates itself from write-oriented siblings such as request_free_brief, create_share_link, and create_checkout_link by declaring it 'only returns links' and 'sends nothing and creates nothing.' An agent can route correctly without opening the schema.

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?

Gives a concrete precondition and sequencing rule: 'Send the person's email, with their consent, to check that limit before you give them the link.' That is an actionable when-to-use instruction. It stops short of naming the alternative tool (request_free_brief) for the case where the agent actually needs to submit a request, so it is clear context rather than full when/when-not/alternatives coverage.

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