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

No annotations exist, so the description carries the full burden and does well: it declares zero arguments, discloses that the map is rebuilt from compiled skills on every call (a cost/freshness signal), and defines the empty-state behavior (empty lists plus a 'message' explaining why). It stops short of stating permission requirements or expected latency, so it is strong but not exhaustive.

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 the purpose, then routing, then behavior in a clean progression. The closing sentence detailing the return shape ({nodes, edges}, kind/rel enums) partially duplicates the output schema, so it is slightly longer than strictly necessary, but no sentence is wasted.

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 zero-parameter, read-only map tool with an output schema, the description covers purpose, routing, argument count, rebuild semantics, and the empty-result case. Nothing an agent needs in order to call it correctly or interpret an empty response is missing.

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 tool takes zero parameters, which is the baseline-4 case; the description reinforces this with 'It takes no arguments.' Nothing further is needed on this dimension.

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 ('map how the company works: procedures, tools, docs') and immediately disambiguates against the two nearest siblings, get_skill and get_graph. An agent can tell exactly which tool answers 'big picture' questions 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?

Gives explicit when-to-use framing with concrete example questions ('which processes touch Jira?', 'what do we run through Slack?') and routes users to get_skill for a single procedure's steps and get_graph for the topic graph. Both the use case and the alternatives are named, not implied.

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