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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description still adds real behavioral value beyond them: it lists the returned fields and clarifies that 'updatedAt is the last edit, not the last save' and that draft changes are surfaced — a subtlety an agent could not infer from annotations or an empty 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?

Three tight sentences, front-loaded with purpose and return contents, then the usage condition, then a caveat. No filler and nothing repeated from the title.

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?

With no output schema, the description correctly does double duty by enumerating returned fields, and it covers invocation context. Minor gaps remain: nothing about ordering of results or behavior with an empty catalog, though for a zero-parameter read tool these are small.

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 there is nothing for the description to disambiguate; baseline is 4 by rule. The description adds no parameter information, but none is needed.

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 ('List the services in your microservice.md catalog') and enumerates exactly what comes back: ID, name, mission, team, saved version, and draft-change status. The mention that it is the fallback when the repo lacks a MICROSERVICE.md with a Catalog ID line implicitly separates it from the sibling get_service_md.

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 a concrete when-to-use condition ('to find a service_id when the repo has no MICROSERVICE.md with a Catalog ID line'), which is actionable context. It does not name the alternative tools (get_service_md, list_artifacts) or state when not to use it, so it stops short of full routing guidance.

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