swsd_get_category

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile needs no restating. The description adds only that children/subcategories come back with the record, which is modest extra context and largely overlaps with the existing output schema; nothing about error behavior for unknown ids is given.

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 sentences, no filler, and the retrieval purpose is front-loaded before the prerequisite hint. Every clause carries information the agent can act on.

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 single-parameter read with a full output schema and complete annotations, the description covers purpose, returned fields and the id-provenance prerequisite. Only an error/missing-id note is absent, which is a minor omission rather than a blocking 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?

With 100% schema coverage and only one parameter, the schema already explains that id is the SWSD record id from a swsd_list_* tool. The description reinforces the lookup pattern but adds no format or constraint detail beyond the schema, so the 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 specific verb and resource ("Fetch one SWSD category by id") and names the payload returned (subcategories/children, parent_id, default_assignee_id), which distinguishes it from the sibling swsd_list_categories by scope and from other swsd_get_* tools by resource.

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?

Explicitly routes the agent to swsd_list_categories when the id is unknown, which is the main ambiguity for a get-by-id tool. It does not spell out a when-not-to-use condition (e.g., browsing the whole tree), so it stops short of the full 5.

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