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

Annotations already declare readOnly=false, destructive=false, idempotent=false, and openWorld=true, so the safety profile is covered. The description adds genuinely new behavior beyond the schema: Eventee fetches the photo server-side from photo_url, an external side effect an agent should know about. It stops short of stating duplicate-email behavior or permission requirements, which matters given idempotentHint=false.

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, front-loaded with the WRITE marker, then the workflow link, then the one non-obvious parameter caveat. No filler and nothing to trim.

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 14 params, no output schema, and only one required field, the description covers the essentials plus the return-value hint ("returned id"), which is valuable since no output schema exists. The remaining gap is error/duplicate behavior for a non-idempotent write.

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% with 14 well-documented properties, so the schema carries the parameter burden. The description adds real meaning only for photo_url (server-side download), leaving the other 13 fields entirely to the schema — appropriate, but the baseline is the correct score.

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?

Opens with an explicit verb+resource marker ("WRITE: add a speaker profile to the event") plus the user-visible consequence ("shown in the event app"). Among siblings it is unmistakably the speaker-creation tool versus create_session/create_hall and the read-only list_* tools, and it names the downstream link to sessions.

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 gives forward-looking workflow guidance ("Use the returned id in speaker_ids of a session"), which tells the agent where this fits in a sequence. However, it never states when not to use it, what to do if the speaker already exists, or whether a separate update path exists — usage is implied rather than specified.

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