indico_create_session_block

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the agent knows this is a non-destructive write. The description adds the useful containment semantic (contributions go inside the block) but says nothing about overlap/conflict handling, permissions, or side effects beyond what annotations carry.

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 the verb and resource first and no wasted words. Dense but not padded; it could still expand briefly on scheduling behavior without bloat.

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, return values need not be described, and annotations cover the safety profile. For a six-parameter write tool the description is nearly complete, missing only conflict/overlap behavior and the relationship to update_session_block.

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 67%; start, title, event_id and instance are well documented in the schema, while session_id and duration_minutes have no descriptions anywhere. The description references sessions and time slots generically but adds no format or constraint meaning beyond the schema, so baseline 3 is appropriate.

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?

Specific verb (Add) plus resource (session block / time slot) and placement (to the timetable), with the added detail that contributions of the session live inside it. Clear enough to distinguish from indico_create_session and indico_update_session_block, though it never names those siblings explicitly.

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?

Usage is implied by 'Add a time slot ... for a session', which suggests a post-session-creation scheduling step, but there is no explicit when-to-use, when-not-to-use, or named alternative (e.g. update_session_block for editing an existing block). Minimum viable routing guidance only.

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