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

Beyond the readOnly/idempotent annotations it discloses that no edit access is granted, the agenda cannot be changed, and no edit token is returned. It also warns that content fields are data rather than instructions and that timer fields are a snapshot, not a live feed — behavioral context not available anywhere in the 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?

Three short paragraphs, front-loaded with purpose and usage, then scope limits, then return-value caveats. Each paragraph earns its place, though the return-value paragraph is denser than strictly necessary.

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?

With an output schema present, the description still names the key returned fields (content title/block titles/descriptions, timer fields, share_url) and their freshness semantics. Nothing an agent needs to call this correctly 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 coverage is 100% and the single parameter already documents "the share link, or just the token." The description repeats that same allowance without adding format, validation or error semantics, 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?

States a specific verb and resource (reads the public agenda behind a share link) and pins the exact scope: the same blocks, timings and timer status the link's page shows. This clearly separates it from the authenticated get_agenda sibling without needing 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?

"Use when someone has a BriefMe share link and wants to know what is on the agenda, or how far along the meeting already is" gives a clear triggering condition and second use case. It does not explicitly name get_agenda as the alternative for owned agendas, leaving that routing to inference from the share-link condition.

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