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

Annotations declare destructiveHint=true, yet the description never explains what is destructive about updating fields or which updates are irreversible. Beyond announcing a mutation, the description adds nothing about required permissions, side effects, or behavior when fields are omitted, so it is redundant against the annotations.

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?

A single front-loaded sentence with no wasted words. Its brevity is clean structurally, though it verges on under-specification rather than genuine economy.

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 an 8-parameter mutation tool with destructive behavior, no output schema and sparse annotations, the description omits what fields can be updated, the meaning of destructive, and usage routing. It is not complete enough for an agent to invoke correctly with confidence.

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 only 25% (just meeting_id and workspace_id are documented), leaving date, name, summary, transcription, meeting_type_id and meeting_group_id unexplained. The description generically references 'campos' without naming or clarifying a single parameter, so it fails to compensate for the coverage gap.

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+resource ('Actualiza campos de una reunión existente'), clearly distinguishing it from create_meeting, delete_meeting or get_meeting. It does not, however, differentiate itself from close siblings such as update_meeting_type or update_event, so it falls short of a 5.

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?

No when-to-use guidance and no mention of alternatives (e.g., update_meeting_type for type changes, update_event for calendar entries). The agent gets no condition that selects this tool over its siblings.

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