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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the read-only safety profile needs no repetition. The description adds valuable behavior context beyond annotations: it resolves live metadata, works with specific metadata formats, and gives a concrete SharePoint example. It does not describe pagination or error behavior, but those are not critical for a read-only resolve operation.

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 tight sentences: define the action, state the exact trigger, then give metadata types and an example. No wasted words, the most important guidance is front-loaded, and every sentence contributes to successful invocation.

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 12-parameter tool with no output schema, the description plus fully described schema parameters leaves little ambiguity about what input is required and why. The main gap is that the return shape is not explicitly described, but the schema's includeRaw, propertyName, and contextParameterAlias parameters implicitly clarify the response behavior.

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%, so the schema already explains each parameter well. The description adds meaningful workflow guidance beyond the schema by explaining the progressive propertyName/includeRaw=true follow-up pattern and by grounding the parameters object in a realistic SharePoint site/list/view example.

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 opens with a specific verb and resource ('Resolve live dynamic schema/properties for a connector operation parameter') and immediately ties it to a concrete trigger from describe_live_connector. It clearly separates this tool from the sibling get_live_dynamic_options by scoping it to dynamicProperties and x-ms-dynamic-properties/x-ms-dynamic-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?

It states an explicit use condition: call this when describe_live_connector returns a dynamicProperties entry with nextTool=get_live_dynamic_properties. This is strong guidance for when to invoke the tool. It does not explicitly mention when not to use it or name alternatives like get_live_dynamic_options, but the trigger is sufficiently clear and directive.

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