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

Annotations already declare openWorldHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is partly covered. The description adds genuine value beyond that: it discloses the data goes to an external sales team via a known form, that the result is a scheduling link rather than a confirmed booking, and the 'only use provided details' consent constraint. It stops short of saying whether the lead is emailed, stored, or how long the link is valid.

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?

Two sentences with no filler: the action and outcome come first, the data-provenance constraint second. Nothing repeats the title or the schema, and the parenthetical URL is short and load-bearing.

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 seven-parameter mutation with full schema coverage and no output schema, the description covers what it does, where the data goes, what the caller receives (a link), and the consent constraint. A minor gap remains around post-submission behavior (confirmation, follow-up, failure modes), which an agent handling an external side effect would benefit from knowing.

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 all seven fields carry per-field descriptions with enums, so the schema does the heavy lifting. The description adds only the aggregate framing ('a brand's details') and the provenance rule, not field-level meaning beyond what is already documented.

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 and resource ('Submit a brand's details to MadBroad's sales team') and names the concrete outcome ('get a link to pick a time for the intro call'), plus an equivalence anchor ('the same form as madbroad.co/book-meeting'). An agent can tell exactly what this does and what it produces, and none of the siblings (list_case_studies, get_role, apply_video_editor, etc.) overlap.

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 constraint 'Only use details the person has provided' is a real usage rule, implying this should only be invoked with user-supplied contact info rather than inferred data. However, there is no explicit statement of when to invoke it (e.g., only after the brand expresses interest in street interviews) and no named alternative or when-not condition.

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