parse-teams-url

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

Annotations include readOnlyHint: true, and the description reinforces this by describing a parsing/conversion operation with no side effects. It adds value by detailing the input formats (short, full, recap) and output (joinWebUrl).

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, no extraneous words. Front-loaded with purpose, followed by usage guidance. Every sentence is actionable and informative.

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 states the output is a standard joinWebUrl, which is sufficient. It also references the downstream tool (list-online-meetings), completing the usage context. All essential information is present.

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 single parameter 'url' has a schema description, but the tool description enriches it by enumerating valid format examples (short /meet/, full /meetup-join/, recap ?threadId=), covering all variations beyond the schema's generic description.

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?

Description explicitly states 'Converts any Teams meeting URL format... into a standard joinWebUrl', providing a specific verb and resource. It distinguishes from sibling tools by referencing 'list-online-meetings' and specifying when to use this tool.

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?

Directly advises to use this tool before list-online-meetings when the user provides a recap or short URL, giving clear context on when to invoke it and implicitly when not to.

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