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

No annotations are provided, so the description carries the full behavioral burden, and it discloses nothing: not whether the guide is static or query-filtered, not how large the response is, not whether it is safe/read-only, and not what the optional query does. "(knowledge)" is a label, not 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?

It is short, but this is under-specification rather than conciseness: the text is a fragment with no predicate, and the namespace/name prefix duplicates information the caller already has from the tool identifier. It is neither front-loaded nor informative.

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 knowledge-lookup tool with one optional parameter and no output schema, the description should at minimum say what content the guide covers and when to consult it versus the sibling `.plan` tools. None of that is present, so an agent cannot reliably decide whether to invoke it or what it will receive.

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 optional `query` parameter is fully documented in the schema (100% coverage, maxLength 500), so per the rubric the baseline is 3. The description adds nothing about how the topic string is matched or what happens when it is omitted.

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?

"mediasfu-shared :: backend.integration.guide (knowledge)" merely restates the tool's own name plus the tag "knowledge"; there is no verb and no statement of what the tool actually does. It does hint that this is a reference/guide lookup rather than a mutation, but that is inference from the identifier, not from the description.

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 prerequisites, and no mention of alternatives such as shared::integration.plan, shared::headless.integration.plan, or shared::api.reference.search. An agent has no basis for choosing this guide over any of the many sibling planning/reference tools.

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