phabricator_blog_search

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

Annotations already declare readOnlyHint=true, so safety is covered, but the description adds nothing else — no note on pagination semantics (after/before cursors), what 'attachments' change about the payload, or how queryKey presets interact with constraints. Only a bare restatement of the operation is given.

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 words, front-loaded, zero waste. Brevity here borders on under-specification rather than verbosity, but nothing in the text is filler.

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?

Seven parameters including two nested objects, no output schema, and a sibling that searches a very similar resource — this tool needs at least a sentence on scope and the blogs-vs-posts distinction to be safely selected. The single phrase leaves that gap entirely unfilled.

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 description coverage is 100% and every parameter (cursors, limit, order, queryKey enum values, attachments, constraints) is documented inline. The description contributes no additional meaning, so the baseline 3 applies.

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 and resource ('Search Phame blogs'), so an agent knows it is a read lookup of blog containers. It does not distinguish itself from the adjacent phabricator_blog_post_search, however, and 'Phame' is internal jargon an agent may not resolve without help.

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 gives no when-to-use guidance, no exclusions, and no mention of the obvious alternative (blog_post_search for posts vs. blogs). An agent has to infer the distinction from tool names alone.

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