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

Beyond the annotations (which only say write, non-destructive, open-world), it discloses the created status (New), that Rent Manager can notify the assignee and tenant by its own rules so the call reaches other people, the default per-call confirmation with an opt-out, and the required API key scope. That is exactly the behavioral context a mutation tool needs.

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?

Core purpose is front-loaded, but the text is redundant: 'Open a service issue...' is restated as 'Opens a service issue... with the status New', and the 'reaches other people / confirm before each call' warning is repeated twice in slightly different words. Several sentences fail to earn their place.

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?

No output schema exists, and the description still covers what is created, its initial status, side effects on other people, confirmation policy, and auth requirements. It lacks error behavior or any hint of the returned identifier, keeping it just short of fully complete.

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 coverage is 100%, so the baseline is 3. The description explains the intent of tenant_id and assigned_to (reporter vs. assignee), but this largely restates what the schema descriptions already convey and adds no syntax or format detail for the other parameters.

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+resource ('Open a service issue') and adds concrete scope: for a property and unit, created with status New, optionally assigned and scheduled. An agent can immediately tell this apart from rent-manager_list_service_issues and rent-manager_update_service_issue.

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?

Gives clear context for optional parameters ('Give tenant_id to tie it to the tenant who reported it and assigned_to to give it to a Rent Manager user') and states the confirmation requirement. It does not explicitly compare against sibling tools like update_service_issue, so it falls short of full when/when-not guidance.

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