notion_list_templates

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

No annotations are provided, so the description carries the full burden. 'List' plus 'inspect' imply a read-only operation, and it usefully discloses the 'default' sentinel value, but it says nothing about permissions/plan requirements, pagination, or result count/order.

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 purpose sentence followed by the workflow hint, then a compact two-line parameter glossary. Every line carries information and nothing is padded.

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?

With an output schema present, return values need no explanation; the description covers purpose, both parameters, and the downstream call. Only access prerequisites and pagination behavior are absent, which is minor for a two-parameter list tool.

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?

Schema coverage is 0%, so the description must compensate, and it does: database_id is identified as 'the database to inspect' and name is documented as an optional case-insensitive substring filter — the case-insensitivity is genuine meaning the schema lacks. The database_id explanation is thinner than the name one, keeping it short of a 5.

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 ('List the page templates defined on a database') and immediately frames the output's purpose by pointing to notion_create_page's template argument, which separates it from sibling list/search tools like notion_list_views or notion_query_database.

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 a concrete follow-up workflow (pass the returned ID, or the literal 'default', as notion_create_page's template argument), which tells the agent when this tool belongs in a sequence. It does not state when NOT to use it or contrast with notion_describe_database, so no exclusions are covered.

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