mdl_feeds_hide

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

Annotations already declare readOnlyHint=false and destructiveHint=false, and the description correctly reinforces the mutating nature ('Changes data on MyDramaList'). It adds genuinely useful context beyond the annotations: the host-configured authentication requirement and the explicit-user-request constraint. It does not clarify reversibility of hiding, which is a minor gap.

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?

Three short clauses, no filler, and the purpose is front-loaded. Efficient, though the leading fragment 'Feeds: hide.' is telegraphic rather than explanatory.

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 single-parameter mutation with no output schema, the auth and safety guidance is adequate, but the complete silence on the required feed_id leaves the agent without enough to construct a correct call.

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 feed_id parameter has 0% schema description coverage, and the description says nothing about it — not its format, source, or how to obtain it. With one undocumented required parameter, the description fails to compensate for the schema gap.

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?

States a specific verb+resource ('Feeds: hide'), which an agent can distinguish from siblings like mdl_feeds_delete, mdl_feeds_edit, and mdl_feeds_like. However, it never explains what 'hide' actually means relative to delete/remove, so the boundary is only implicit.

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?

'Use only for an explicit user request' gives a clear gating condition for invocation, but there is no guidance on when to prefer hide over the sibling operations (delete, edit) or any prerequisites beyond auth.

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