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

Annotations already indicate a write operation, but the description adds valuable behavioral context: the listing is only a draft, it is subject to moderation, and university_id/campus_id are intentionally kept NULL. This goes beyond the schema and annotations, helping the agent understand the side effects and data model.

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?

The description is two sentences, front-loads the core action, and adds one crucial non-obvious detail. There is no filler or repetition of schema information.

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 18 parameters, a nested object, no output schema, and minimal schema descriptions, the description is too sparse to fully prepare an agent. It does not explain moderation workflow, expected response, or the semantics of key parameters beyond a generic listing creation context.

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 11%, so the description carries a heavy burden for explaining parameters. It does not explain the meaning or expected format of most of the 18 fields, apart from the location-independence concept. The description does not compensate for the sparse schema documentation.

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 uses a specific verb ('Create') and resource ('UniAffitti listing draft for moderation'), making it clear that this is a creation tool rather than a read or request tool. It also distinguishes this from create_rental_request by stating the result is a listing draft, not a request.

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?

The description implies this tool is for creating listings that will be moderated, so an agent can infer when it applies, but it does not explicitly state when to avoid it or compare it to siblings like create_rental_request. The note about university_id and campus_id being intentionally NULL provides some operational guidance, but not explicit routing.

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