get_collection_manifest

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

The description discloses behavioral traits beyond annotations: caching behavior ('Returns cached MANIFEST.json if available, otherwise generates on-demand'), read-only nature ('metadata extraction only, no skill generation'), and failure mode ('On failure returns {"error": str}'). This aligns with the readOnlyHint annotation and adds valuable context.

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 description is very concise: three sentences that front-load the core purpose, then detail caching and failure behavior. Every sentence adds value, with no wasted words.

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?

Given the simple input (one required parameter, no enums), presence of an output schema, and clear description of return values (success and error cases), the description is complete. It explains what the tool returns and under what conditions, without needing to duplicate output schema details.

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 single parameter 'collection_namespace' has 100% schema coverage with a clear description including an example ('e.g. 'netbox.netbox''). This adds meaning beyond the schema by providing a concrete format, which helps the agent correctly invoke the tool.

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 clearly states 'Get collection-level manifest with per-module summaries.' This specifies the verb (get), the resource (collection-level manifest), and the scope (per-module summaries), distinguishing it from sibling tools like get_module_doc or get_skill that target specific components.

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 does not provide explicit when-to-use or when-not-to-use guidance. It implies usage for retrieving manifest data, but there's no comparison with siblings like get_collection_docs or search_collections. The context signal of sibling tools is present but not leveraged in the description.

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