perspective_get_embed_options

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

Describes a non-destructive retrieval operation, listing what is returned, but lacks disclosure of permissions, rate limits, or response format. Without annotations, the description carries full burden and is minimally transparent.

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?

Single sentence, front-loaded with the action and key details, no wasted words.

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 retrieval tool, the description conveys the main output (embed snippets list and SDK reference). However, it lacks detail on the format of the snippets or SDK reference, which could be important for an agent.

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?

No parameters exist (schema coverage 100%), and the description adds value by enumerating the embed snippet types, providing context beyond the empty schema.

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?

Describes a specific verb 'Get' and resource 'embed snippets' with a list of types (fullpage, widget, popup, slider, float, card) and 'SDK reference', clearly distinguishing from sibling tools that create, update, or list perspectives.

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 implies usage for retrieving embed options, but does not explicitly state when to use this tool over alternatives or provide any exclusions or preconditions.

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