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

No annotations are provided, so the description carries the burden. It discloses the access scope (owned + shared) and the returned tagging (role, MCP slug when published), which is useful behavioral context. But it omits permissions required, pagination behavior, and result limits — meaningful gaps for a listing tool with zero annotation coverage.

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?

One dense sentence, front-loaded with the verb and resource, that also carries the scope and return-shape detail. No waste.

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 no-param listing tool with no output schema, the description covers what is returned (graphs, access role tags, MCP slug) and the visibility scope. It is nearly complete, missing only pagination/ordering behavior.

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?

Zero parameters, so the schema contributes nothing and there is nothing for the description to document. Per the rubric, a 0-param tool has a baseline of 4.

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 (list) and resource (graphs) with precise scope — the caller's own graphs plus those shared with them. This clearly distinguishes it from get_graph (single graph) and list_templates (templates), so the agent can tell the siblings apart.

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?

Usage is implied by the plural 'list' and the scope statement, but there is no explicit when-to-use/when-not guidance or naming of alternatives (e.g., get_graph for a specific graph). Adequate, not rich.

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