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

Adds substantive behavior beyond the annotations: the auth requirement (Remote Vegas agent token in the HTTP Authorization header, error without one) and the fact that submissions are queued for human moderation before counting. These are exactly the operational facts an agent cannot derive from readOnlyHint=false / 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 compact sentences, front-loaded with the auth gate, then the use condition, then the moderation caveat. The partial '(workability 1-5, Wi-Fi, outlets, noise…)' enumeration trails off rather than resolving, but nothing is padding.

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 an 11-parameter write tool with no output schema, the description covers the critical unknowns: authorization, moderation latency, and the epistemic bar for values. It stops short of saying what a successful response contains or whether repeat check-ins at the same spot are allowed (idempotentHint=false).

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 27% across 11 parameters, so the description must compensate and it only partly does: it names workability 1-5, Wi-Fi, outlets and noise, leaving calls, crowd, light, seating, speed_mbps, note and slug meaning to the enums and terse schema text. The 'today' and 'never infer' framing usefully constrains values but doesn't explain the remaining fields.

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 pairs the verb 'report'/'check in' with a precise resource and scope: today's in-person observed conditions at a spot. It implicitly separates itself from update_spot_facts by insisting on first-hand observation rather than curated facts, but it never names that sibling 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?

Strong, explicit gating: 'Partner agents only' with a token requirement, 'Use only to report conditions the user observed IN PERSON ... today', and 'Never invent or infer values' tells the agent exactly when not to call. What's missing is a named alternative for non-first-hand or historical data (e.g. update_spot_facts).

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