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

The annotations already define the safety profile, and the description adds important operational context not present there: the required Authorization header and POST-only constraint. It still does not describe return format, pagination, or error behavior.

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 definition is compact and front-loads the intended role, queue contents, auth requirement, and POST-only constraint without filler. The role-first opening slightly delays the core verb, but the structure remains clear.

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 zero-parameter queue tool with no output schema, the description covers the key facts needed to invoke it: who it is for, what it returns in broad terms, how it authenticates, and the HTTP method. Pagination or error details would be nice, but are likely unnecessary here.

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?

There are zero parameters, so the baseline is 4. No parameter semantics are needed, and the description does not introduce misleading parameter expectations.

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 identifies a specific resource, the mayor's domain queue, and enumerates its contents: open suggestions, held discussion posts, and held visit reports. It scopes the tool to a Deputy of a Neighborhood Mayor, but does not explicitly distinguish it from siblings such as get_suggestion or get_visit_reports.

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 clearly states the intended role and prerequisite authorization, including that the Bearer deputy token is issued by the mayor on their desk. It also specifies POST only, giving clear usage context, though it does not name alternatives or when-not conditions.

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