Inspect component manifest

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

Beyond the annotations (readOnlyHint, destructiveHint), the description adds valuable behavioral context: it 'reports validation problems instead of throwing.' This discloses error-handling behavior not captured by the annotations. It also clarifies the input scope ('package folder or file') and what is checked (metadata, declared assets, docs), adding meaningful transparency.

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 concise at two sentences, front-loaded with the core action, and every clause adds value. No redundant or filler content exists. It efficiently packages purpose, usage context, and error behavior without 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?

For a simple validation tool with a single parameter and strong annotations, the description is largely complete. It explains what the tool does, when to use it, and its error-handling approach. The only minor gap is that it does not describe the return value on success, but given the tool's simplicity and no output schema, this is not a major deficiency.

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 0% schema description coverage, the description needed to explain the 'path' parameter. It does say 'from a package folder or file,' which clarifies that path can reference either a folder or a file. However, it lacks details like accepted formats, relative vs absolute paths, or examples, so it only partially compensates for the absent schema 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 clearly states the tool's function: 'Read and validate a tdmcp component/library manifest from a package folder or file.' It specifies the verb (read and validate), the resource (manifest), and the scope (package folder/file). It also distinguishes this tool from related tools by framing it as a pre-installation check for install_library_package and make_portable_tox, making its unique purpose evident.

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 explicitly says to use this tool 'before install_library_package or make_portable_tox', giving clear when-to-use context. It does not explicitly name alternatives or provide when-not-to-use guidance, but mentioning the two dependent tools is sufficient context for an agent to select this over more general inspection tools.

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