get_figure_v1_figures__figure_id__get

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

With no annotations provided, the description fully covers behavioral traits: public vs private access, 404 for non-owners, optional auth, and is_liked_by_me reflecting user status. It does not mention rate limits or side effects, but for a read-only tool this is sufficient.

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 well-structured with sections for return details, visibility, and authentication. It is concise and front-loaded with the core purpose, with every sentence adding value.

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 the tool's simplicity (one parameter, no output schema), the description completely covers return fields, visibility rules, and auth behavior. No obvious gaps exist.

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 only parameter figure_id has no description in the schema (0% coverage). The description says 'by UUID' implying a format, but no detailed format or constraints are given. It adds minimal value beyond the parameter name and type.

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 'Get a figure by its UUID.' The verb 'get' and resource 'figure' are specific, and the use of UUID distinguishes it from list endpoints like list_figures.

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 explains visibility rules and authentication needs, providing clear context on when the tool returns data and for whom. However, it does not explicitly contrast with siblings like list_figures or create_draft_figure.

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