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

Annotations already declare readOnlyHint=false, idempotentHint=false and destructiveHint=false, so the bar is lower, and the description still adds the consequence of the non-idempotency ('calling it twice logs two requests') plus the downstream workflow (staff convert it into a job). It does not cover authorization requirements or what the response contains, which keeps it from a 5.

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 and the request-versus-job distinction, with the endpoint as a trailing implementation hint. No filler sentences.

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 six-parameter write tool with full schema coverage and no output schema, the description covers mode, idempotency and domain role adequately. The one remaining gap is that it never says what a successful call returns (presumably the created request with an ID), which matters for a create operation with no output schema.

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% and every parameter carries its own description, enum, or format constraint, so the schema does the heavy lifting. The description adds no parameter-level meaning such as defaults for priority or reported_at, so baseline 3 applies.

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 concrete verb and resource ('log a maintenance request against a property') and immediately disambiguates the most likely confusion, that a request is not a job. An agent can distinguish this from the maintenance-job siblings without opening any schema.

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 'a request, not a job: Street staff turn it into a job' clause tells the agent which workflow stage this belongs to and implicitly routes job-level operations elsewhere. It stops short of naming an alternative tool or stating explicit exclusions, so it lands just below the top band.

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