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

No annotations are supplied, so the description carries the full behavioral burden, yet it discloses no side effects, no read/write nature, and no output shape beyond the marketing phrase 'prompt pack with examples.' Marketing copy ('production-ready', 'you can run today') occupies the space where behavioral disclosure should be.

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?

Only two sentences, so it is short, but both are promotional rather than informative and none of the words help an agent decide or call correctly. Front-loading is fine; the content of the lead sentence is the problem, not the length.

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 annotations, no output schema, and a single loosely described parameter, the description is the only source of behavioral information and it provides none about results or failure modes. For a library-style retrieval tool the agent cannot tell what content comes back or how it differs from the sibling libraries.

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?

Schema coverage is 100% and the single optional 'query' parameter is documented in the schema as scoping the analysis, so the baseline of 3 applies. The description adds nothing about how the query is interpreted or what scope it narrows.

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 restates the name ('mkt problem library system') and then sells a deliverable ('copy-paste prompt pack with examples') rather than stating what invoking the tool actually does or produces. It never distinguishes this library from close siblings such as mkt-scene-library, mkt-situation-library, mkt-campaign-library, or mkt-sop-core, which an agent must choose between.

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?

There is no when-to-use guidance, no exclusion criteria, and no named alternative. The audience note ('for marketing and operations leaders') is context about people, not about the task conditions that select this tool over the four sibling mkt-* libraries.

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