get_all_sessions

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

No annotations are provided, so the description carries the full behavioral burden. It transparently discloses the caching behavior: 15-minute expiration, automatic refresh on the next request, and the ability to force refresh with refresh=true. This goes beyond a simple fetch and helps the agent understand side effects and timing.

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 sentences with no filler. The main action is front-loaded, followed by the key behavioral caveat (cache expiration) and the parameter hint. Every sentence earns its place.

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 simple tool with one optional parameter, no annotations, and no output schema, the description covers the essential points: what it fetches, caching behavior, and how to override the cache. It does not mention return format or large-result handling, but that is a minor gap for this scope.

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 input schema has 100% description coverage for the single refresh parameter, so the baseline is 3. The description reinforces the same information ('Use refresh=true to force immediate refresh') without adding meaning beyond what the schema already provides.

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: 'Fetch all Microsoft Ignite sessions' — exactly what the tool does. It is clearly distinguished from siblings like get_session_details (singular) and search_sessions (filtered) by emphasizing 'all'.

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?

Provides clear context: this tool is for retrieving the complete set of sessions, as opposed to a single session or a search. It does not explicitly name alternative tools, but the 'all' scope makes the intended use evident.

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