get_capabilities

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

The annotations already establish that the operation is read-only, idempotent, non-destructive, and closed-world. The description adds useful context by enumerating the manifest contents and stating that it is a once-per-session call, though it does not detail response structure or caching behavior.

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 sentences, front-loaded with 'Manifest:' and immediately followed by the practical call guidance. The enumerated capabilities are dense but necessary, and there is no wasted prose.

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 no-parameter, read-only discovery tool with rich annotations, the description gives enough to understand what it returns and when to invoke it. It could be stronger by clarifying how it relates to siblings like list_tools or describe_tool, but no critical calling information is missing.

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 has zero parameters and an empty input schema, so there are no parameter semantics to clarify. A baseline of 4 is appropriate because the description does not need to compensate for missing parameter documentation.

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 identifies a specific resource: a manifest covering operation categories/counts, edit-action types, mask types, formats, backends, security policy, workflows, and error codes. It is clearly a capabilities-discovery tool rather than a tautology, though it does not explicitly distinguish itself from siblings such as list_tools or describe_tool.

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 explicitly says to call it once at the start of a session, which gives clear timing and frequency guidance. It does not state when not to use it or name an alternative for already-known capabilities, so it falls short of full when/when-not routing.

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