get_category

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

Annotations already declare readOnlyHint=true, and the description 'Get category by ID' is consistent with that read-only intent. The description adds no additional behavioral context (e.g., not-found behavior, permissions), but the annotation covers the key safety trait, so a baseline 3 is appropriate.

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 short, front-loaded sentence states the action, resource, identifier, and source with zero wasted words. It is as concise as possible while remaining informative.

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 simple one-parameter read tool with an output schema and readOnlyHint, the description is nearly complete. It lacks any pointer to related tools or return expectations, but those are reasonably covered by the sibling names and output schema, leaving only a minor 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?

The input schema fully describes category_id as a UUID string with 100% coverage. The description merely echoes 'by ID' without adding deeper meaning, so the schema carries the semantic weight and 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?

The description uses a specific verb ('Get'), resource ('category'), identifier ('by ID'), and source ('from Document360'), making the core operation clear. It does not explicitly differentiate from sibling get_category_page_content, but the resource and name distinction is sufficient for a 4.

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 is provided on when to use this tool versus alternatives like get_category_page_content or get_article. There are no conditions, exclusions, or supporting context, so usage is only implied by the action itself.

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