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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real context beyond them: the response contains a nextAction hint and a missingFields list of exactly which required fields are empty, plus the NOMADSTAYS_MCP_AGENT_TOKEN auth requirement.

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?

Two tight sentences with no filler, and the scope statement is front-loaded ahead of the return-shape and auth details.

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 no output schema, the description usefully discloses the two key return elements (nextAction, missingFields) and the auth prerequisite, so an agent knows what it will get back. It stops short of describing failure behavior for an invalid applicationId, which is a minor gap.

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?

Only one parameter (applicationId) and schema description coverage is 100%, so the schema already documents it fully. The description adds nothing about the parameter, which is the expected baseline when the schema carries the load.

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?

States a specific verb ('Get') and resource ('the full current state of one Coworking Application'), making the singular scope explicit against the many-valued listCoworkingApplications and distinguishing it from the sibling getExperienceApplication/getStayApplication tools.

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 only implied: an agent can infer this is the single-record read versus the list, and the 'if incomplete' phrasing hints at a pre-submit check, but there is no explicit when-to-use/when-not or named alternative in the description itself (the listCoworkingApplications pointer lives in the schema, not the description).

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