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

No annotations are provided, so the description carries the full behavioral burden, and it discloses almost nothing: no auth/permission requirements, no indication of whether the comment is appended vs replacing anything, no notification/mention behavior, no mention of rate limits. It mentions markdown only indirectly in the Args list.

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 purpose is front-loaded in the first sentence, and the Args block is justified because the schema carries zero parameter descriptions. Slightly verbose in the minor redundancy between 'key: The work item key' and the parenthetical example, but nothing wasteful.

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?

An output schema exists, so return values need not be explained. However, for a mutation tool with zero annotations, the description should say more about side effects and permissions; the argument documentation is complete but operational context is thin.

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 compensate, and it does: it documents all three parameters, gives a concrete key format example ('CPD-123'), specifies body is markdown text, and flags workspace as optional. That is meaningful added value over the bare schema.

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 ('Add a comment to a ticket') clearly and unambiguously. There is no sibling comment tool to differentiate from, though it doesn't distinguish itself from update_ticket or note that comments are a separate artifact.

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 description gives no when-to-use guidance, no prerequisites, and no alternative routing (e.g., when to comment versus updating the ticket body via update_ticket). Usage is only implied by the tool name.

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

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

No annotations are provided, so the description carries the full behavioral burden. It says nothing about side effects, whether the created ticket is returned, permission requirements, or what happens with duplicate summaries; only 'Create' implies a mutation. For a creation tool with zero annotation coverage this is a substantial gap.

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 purpose is front-loaded and the Args list is compact with no filler, but it is an unedited Python docstring rather than agent-optimized prose. It is neither wasteful nor notably well-structured.

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?

An output schema exists, so return values need not be explained, and the description does mark the optional parameters. Still, for a mutation tool with no annotations it omits required-vs-optional framing, failure modes, and any usage context, leaving the agent to infer how to invoke it correctly.

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 compensate, and it does name all eight parameters with brief glosses. But several are tautological ('Project ID.', 'Board ID to place the ticket on') and none explain ID formats, how to obtain IDs, or the structure of extra_fields, so it adds only modest meaning over the raw schema.

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 first sentence gives a specific verb and resource ('Create a new ticket in Task360'), so the agent immediately knows what the tool does. However, it does nothing to distinguish it from sibling mutation tools like update_ticket or transition_ticket, so it stops short of a 5.

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 guidance on when to use this tool versus update_ticket, transition_ticket, or add_comment, nor any stated prerequisites such as required permissions or valid project/board combinations. The description is purely a parameter dump with no routing information.

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

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

With no annotations, the description carries the full burden. It usefully discloses that deletion is permanent and irreversible (not a soft-delete), but says nothing about required permissions, whether child items like comments are removed, or whether confirmation is needed.

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?

Front-loaded with the destructive action in a single sentence, followed by a compact Args block. The Args block slightly restates schema field names, but the added descriptions and example 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?

An output schema exists, so return values need no explanation. However, for a destructive, unannotated mutation tool, the description omits the operational context an agent needs: permissions, cascade effects, and recoverability beyond the word 'Permanently'.

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 compensate, and it largely does: it defines 'key' as the work item key with a concrete format example ('CPD-123') and clarifies that 'workspace' is optional. It does not explain what happens when workspace is omitted.

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 and resource ('Permanently delete a ticket'), which is unambiguous and clearly distinct from create_ticket/update_ticket by implication. It never explicitly names a sibling or scoping rule, so it stops short of the 5 tier.

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 guidance on when to delete versus update or archive, no prerequisites, and no mention of an alternative tool. The only usage-relevant cue is the word 'Permanently', which is inferred rather than framed as advice.

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

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

With no annotations provided, the description carries the full behavioral burden. It does disclose that results are scoped to the authenticated user and that workspace falls back to a configured/primary default, but it never confirms read-only semantics, pagination, ordering, or rate behavior for what is presumably a bulk fetch.

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?

One summary sentence followed by a compact args block; the purpose is front-loaded and every line carries meaning. No filler or restated boilerplate.

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?

An output schema exists, so return values need not be described, and both parameters are covered. The remaining gap is that pagination/ordering behavior for a limit-bounded list is unstated, which matters slightly for correct invocation but is not fatal.

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 compensate, and it does: workspace is explained as an optional slug defaulting to the configured or primary workspace, and limit is described as a maximum count with default 50. That adds real fallback semantics beyond the bare property names, though it omits any pagination or offset interaction.

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 and resource with scope: tickets assigned to the authenticated user in a given workspace. That scope implicitly separates it from siblings like search_tickets or get_ticket, but the description never names an alternative, so differentiation is left to inference.

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 explicit when-to-use or when-not-to-use guidance, and no alternatives (search_tickets, get_ticket) are referenced. The scope phrase 'assigned to the authenticated user' implies when it applies, but an agent must infer the routing decision entirely.

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

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

No annotations are supplied, so the description carries the behavioral burden. It discloses that the call returns 'full details' rather than a summary, and 'Retrieve' implies a non-destructive read, but there is nothing about auth requirements, behavior when the key does not exist, or cross-workspace access semantics.

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 short elements: one sentence stating the operation and one arg block. The purpose is front-loaded before the arguments, and there is no filler.

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?

A simple two-parameter read tool with an output schema, so return values need no explanation. The description covers both parameters and the core retrieval semantics; only edge-case behavior (missing key, workspace resolution) is absent, which is minor at this complexity.

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 compensate, and it mostly does: it explains 'key' as the work item key with a concrete example, and explicitly marks 'workspace' as an optional workspace slug. It stops short of saying when workspace must be supplied or what omitting it defaults to.

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 ('Retrieve') and resource ('full details of a specific ticket') and pins down the identifier format with the CPD-123 example. It does not, however, distinguish itself from siblings like search_tickets or get_my_tickets, so an agent must infer the boundary itself.

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 phrase 'by key' implicitly signals this is for direct lookup when the key is already known, as opposed to search_tickets or get_my_tickets. There is no explicit when-to-use statement, no exclusions, and no named alternative to route against.

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

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

No annotations are provided, so the description carries the burden. 'Get available transitions' strongly implies a safe read with no side effects, which is the key behavioral fact, but it never states auth requirements, whether results are workspace-scoped, or what happens with an invalid key. Return format is covered by the output schema.

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 purpose sentence is front-loaded and the Args block is tight with no filler. The Args section partially duplicates the schema, but it is short enough that it does not hurt readability.

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?

An output schema exists, so return values need not be described. Both parameters are addressed. What is missing is the workflow context: how this relates to transition_ticket and what the workspace parameter scopes. Adequate but with clear gaps for a workflow-lookup tool.

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 compensate. It documents both parameters and gives a concrete key format example ('CPD-123') and flags workspace as optional, which is more than the schema offers. However it never explains what workspace resolves or what happens if it is omitted, leaving real ambiguity.

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: 'Get available status workflow transitions for a ticket.' The scope (status workflow transitions for a given ticket) is clear and distinguishes it from get_ticket, though the sibling transition_ticket (the write counterpart) is never named or contrasted.

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 infers this is the read-only lookup to call before transition_ticket, but the description never says when to use it, nor when to prefer transition_ticket. No exclusions or prerequisites are stated.

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

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

No annotations are provided, so the description carries the full burden. 'Get' implies a read-only operation and 'current signed-in' usefully signals that the result is scoped to the authenticated user with no way to look up arbitrary users, but permissions, error behavior on missing auth, and caching are unstated. An output schema exists, so return-value detail is not needed here.

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?

A single front-loaded sentence with no filler; the identity of the target user is stated up front. It is terse to the point of under-specification, but nothing in it is wasted.

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 read tool with an output schema, the description covers the essentials: what is returned (profile and details) and whose profile it is. Only the authentication precondition and failure behavior are left unaddressed.

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?

The tool takes zero parameters, so the baseline is 4. Schema description coverage is 100% and there are no parameters to disambiguate, leaving nothing for the description to compensate for.

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 and resource: retrieve the profile of the currently signed-in Task360 user. It is clearly distinguishable from sibling tools like get_ticket or list_workspaces, though it does not explicitly name any sibling to contrast with.

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?

No guidance on when to use this tool versus alternatives, no preconditions, and no exclusions. The phrase 'signed-in' implies it requires an authenticated session but this is never stated as a requirement.

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

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

With no annotations, the description carries the full burden. It does disclose that results are scoped to the authenticated user, implying an auth requirement, but says nothing about ordering, pagination, or whether the list can be empty.

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?

A single front-loaded sentence with the verb, resource, and scope; no filler or redundant restatement of the tool name.

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?

An output schema exists, so return values need not be explained, and the zero-param surface is fully covered. The only gap is pagination/ordering behavior for potentially long workspace lists.

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?

Zero input parameters, so the baseline of 4 applies. There is nothing for the description to clarify beyond the implicit user scoping, which it already mentions.

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?

Names a specific verb (List) and resource (workspaces) with an explicit scope of 'available to the authenticated user'. No sibling differentiation is offered, but none is needed since all siblings operate on tickets, not workspaces.

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 phrase 'available to the authenticated user' implies this is a discovery/enumeration call, but there is no explicit when-to-use guidance, no prerequisites, and no mention of alternatives since there are no other workspace tools to disambiguate against.

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

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

With no annotations, the description carries the full behavioral burden, and it discloses little beyond the schema. The limit default (50) is already in the schema, and nothing is said about pagination, result caps, permission/scope requirements, or whether workspace is required to see results.

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 purpose sentence is front-loaded and the Args block is terse and scannable, with no wasted prose. The structured arg list is slightly redundant with the schema but earns its place given 0% schema description coverage.

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?

An output schema exists, so return values need not be explained, and all parameters are named. However, the absence of annotations plus missing routing guidance and pagination/scope behavior leaves the agent under-informed for a 6-parameter search tool.

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 0%, so the description must compensate, and it documents all six parameters including a concrete JQL-like query example ('status = in_progress', 'assignee = currentUser()'). It leaves gaps such as the valid value space for status_id/project_id, which the schema does not supply either.

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 (search/list) and resource (work items/tickets) with a scope qualifier ('in a workspace'). It does not differentiate from the sibling get_my_tickets, which covers an overlapping retrieval case, so an agent must guess between them.

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?

No when-to-use guidance and no alternatives named, despite siblings get_ticket, get_my_tickets, and list_workspaces covering adjacent retrieval needs. Usage is only implied by the word 'search'.

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

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

No annotations are provided, so the description carries the full behavioral burden. It states a mutation occurs but says nothing about required permissions, side effects such as notifications or comments, whether a transition can fail or be reversed, or what happens to the ticket's other fields.

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 purpose line is front-loaded and the Args block is compact with no redundant prose. Minor overhead from the docstring-style formatting, but every line carries information.

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?

An output schema exists, so return values need no explanation and the three parameters are documented. Still missing behavioral essentials for an unannotated mutation tool: permission requirements, error behavior on an invalid transition_id, and any additional fields the transition may require.

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 compensate, and it largely does: it explains key with a concrete example ('CPD-123'), explains transition_id and how to source it, and marks workspace as optional with its format (slug). It adds real meaning over the bare schema titles.

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?

Specific verb and resource: 'Change the workflow status of a ticket by executing a transition' tells the agent exactly what happens and how. It is clearly differentiated from generic mutations like update_ticket by naming the transition mechanism, though it never explicitly contrasts with that sibling.

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 helpfully points to get_transitions as the way to obtain a transition_id, which is genuine routing guidance for a required parameter. However, it gives no guidance on when to use this versus update_ticket, nor any preconditions for a valid transition.

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

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

No annotations are provided, so the description carries the full behavioral burden, yet it never says whether omitted/null fields are left unchanged or cleared, whether the operation is partial or full-replace, or what permissions are required. The only hint is '(or None)' on assignee_id, which is ambiguous between unassign and no-op.

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 core purpose is front-loaded in one line, followed by a compact Args list. The list partially restates schema field names, but the examples make it earn its place, so there is little waste.

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?

An output schema exists, so return values need not be described. However, for a six-parameter mutation tool with zero annotations, the description is thin on the update semantics and side effects an agent needs before invoking it.

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?

With 0% schema description coverage, the description does the compensating work: it names each field, gives a key format example ('CPD-123'), and shows an extra_fields example ({"board": 1, "sprint": 2}). It falls short of explaining null/unset semantics for assignee_id and whether summary/description overwrite or append.

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 and resource ('Update fields of an existing ticket'), so an agent knows this mutates an existing work item rather than creating one. It does not, however, distinguish itself from siblings like transition_ticket, which can also change ticket state, leaving some selection ambiguity.

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 and no alternatives named, despite a crowded sibling set (create_ticket, transition_ticket, add_comment, delete_ticket). An agent must infer from the name alone whether status changes belong here or in transition_ticket.

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