Get standard change request model

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=true), so that burden is lifted. The description adds value by disclosing error behavior (MissingParameterError when model_sys_id is absent, ParameterError on bad params/JSON) and that the return is a parsed Pydantic model. It still says nothing about pagination, the meaning of the 'Response' wrapper, or why a read tool takes 22 inputs.

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 docstring structure (param/return/raises) is readable and reasonably sized, but the prose is boilerplate-heavy while omitting anything about the vast majority of inputs. It is front-loaded with the purpose, which helps, but it does not earn its space given the schema complexity it ignores.

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 tool with 22 parameters, zero required fields, no output schema, and no parameter-level annotations, the description is far too thin. It never explains how the unrelated-looking IDs interact or what filters apply, so an agent cannot invoke it confidently beyond the single documented argument.

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 0%, so the description must carry the full load, yet it documents only model_sys_id. The other 21 parameters (task_sys_id, change_request_sys_id, worker_sys_id, sysparm_limit/query/offset, etc.) are unexplained in both schema and description, including several that look unrelated to a 'get model' call.

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 gives a specific verb ('Retrieve') and resource ('standard change request model'), so the core operation is unambiguous. However, it offers no differentiation from closely related siblings such as servicenow_get_change_request_models or servicenow_get_standard_change_request_template, leaving the agent to infer which to pick.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives among the many change-request siblings. The only inferable usage is 'call this to fetch a model', which is already implied by the name.

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