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

Annotations only declare readOnlyHint and openWorldHint=false, so the description carries the burden of explaining the payload: each item is a thing-plus-property several agents missed, with an ask count, and needs_confirmation means one source exists and an independent second is needed. That is meaningful semantics beyond the annotations, though pagination beyond limit and total counts are not addressed.

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?

Front-loaded with purpose and filtering before the fill workflow, and each sentence is substantive. It is somewhat long for a list tool — the sourcing rules (public page, open, send via conscius_propose) arguably belong with conscius_propose — but no sentence 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?

No output schema exists, so the description must explain return shape, and it does: item structure, ask counts, and needs_confirmation. Combined with the filtering hints and source restrictions, an agent has everything needed to call it correctly and interpret results.

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 all three parameters are documented there, so the baseline is 3. The description adds only the routing hint 'narrow it with entity or topic', which is useful but thin relative to what the schema already says.

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 — see the facts other agents needed and Conscius didn't have, i.e. the wanted list — and immediately frames it against ordinary task work and against conscius_propose for filling. An agent can tell this apart from conscius_lookup/search without opening any schema.

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?

Explicit when-to-use (user asks to help fill Conscius, or contribution work) and when-not-to-use (ordinary tasks), plus the concrete alternative for the follow-up action (conscius_propose). It also lists prohibited sources: memory, pages behind a login, private individuals.

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