whodb_platform_app_sdks

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint. The description adds genuinely new behavior beyond those: the data comes from a "hosted builder" and workspace targeting is per-call only, "without changing defaults" — a useful scoping detail an agent would otherwise have to guess.

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 sentences, front-loaded with the purpose, followed by the when-to-use and the scoping note. No filler, though the workspace targeting sentence could be slightly tighter.

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?

A read-only list tool with annotations covering safety and no output schema to explain, so the description carries sufficient weight. It could say more about result content or what happens when the optional `name` filter is absent, but nothing critical is missing for correct invocation.

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%, so both parameters are already documented in the schema. The description restates the workspace shape without adding new semantics (e.g. what a valid SDK category name looks like, or behavior when `name` is omitted despite it not being schema-required). 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: "List exact app SDK documentation categories from the hosted builder." Clear what it returns, though it never explicitly distinguishes itself from the singular sibling whodb_platform_app_sdk, leaving the list-vs-lookup distinction to inference.

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?

"Call before writing data or function integration code" gives a clear trigger condition, which is more than most list tools offer. It stops short of naming the alternative tool (app_sdk) or saying when NOT to call it, so it isn't full when/when-not guidance.

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