get_entity_metrics

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

With no annotations provided, the description explains it retrieves stored metrics (read-only) and lists returned fields, but it omits behavioral details such as what happens if the entity does not exist, potential errors, or if any computation is triggered. The description is adequate but not comprehensive.

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?

The description is two sentences, concise and to the point. It front-loads the primary action and lists key return values. No wasted words, though it could be slightly more structured with bullet points or clearer separation.

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?

Given no output schema, the description covers the return values (PageRank, betweenness, etc.). It does not mention error handling or missing entity behavior, but for a simple retrieval tool, the core information is present and sufficient for most use cases.

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 input schema has 100% coverage, so the schema already documents parameters. The description mentions the metrics list but does not add significant semantic detail beyond what the enum and description in the schema provide. Baseline score of 3 is appropriate.

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?

The description clearly states the tool retrieves stored graph metrics for a specific entity and lists the metrics returned. It distinguishes from sibling tools that compute or analyze metrics (e.g., calculate_graph_centrality, detect_graph_communities) by specifying that this tool accesses precomputed values, though it does not explicitly name alternatives.

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 suggests using the tool to understand entity importance and role, but it does not provide explicit guidance on when to use this tool over siblings like analyze_graph_pagerank or get_entity_analytics. No when-not or alternative listing is given.

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